Account security control method, system and device and storage medium

Abstract

The invention discloses an account security control method, system and device, and a storage medium. The method comprises the following steps: obtaining target session information through a preset database according to a target session credential for a target user; determining a target service performed by the target user; obtaining target user information of a target user; the target user information comprises: performing security check on the target service according to the target session information and the target user information to obtain a security check result; if the security check result is passed, executing the target service; and if the security check result is not passed, generating a session exception code, and determining a target processing operation corresponding to the session exception code. According to the method and the device, security control is performed on the account through multi-dimensional transaction risk verification based on the session information and the user information, so that the security of the session is improved.

Description

Technical Field

[0001] This application relates to the field of information security technology, and in particular to an account security management method, system, device and storage medium. Background Technology

[0002] Currently, most internet applications use multi-server deployment to improve system concurrency and robustness. To solve the problem of session state consistency among multiple servers in a distributed system, a common practice is to share sessions, storing session information in a database. However, careless development can easily lead to session corruption, resulting in the leakage of user privacy data and the corruption of transaction data. Furthermore, if the application has security vulnerabilities, such as cross-site scripting vulnerabilities, flaws in the session ID generation algorithm, or storage defects, session hijacking can easily occur.

[0003] Therefore, improving the security of transaction sessions has become an urgent issue to be addressed. Summary of the Invention

[0004] This application provides an account security management method, system, device, and storage medium, which improves the security of account sessions during transactions by performing multi-dimensional transaction risk verification to manage account security.

[0005] In a first aspect, embodiments of this application provide an account security management method applied to a server; the method includes:

[0006] Target session information is obtained from a preset database based on the target session credentials for the target user; the target session information includes: first device information, first user information, and first environment information;

[0007] Determine the target business conducted by the target user; the target business includes any one of the following: credit application business, transaction business, repayment business;

[0008] Obtain the target user information of the target user; the target user information includes: second device information, second user information, and second environment information;

[0009] Based on the target session information and the target user information, a security check is performed on the target service to obtain the security check result;

[0010] If the security check is passed, then the target service is executed;

[0011] If the security check fails, a session exception code is generated, and the target processing operation corresponding to the session exception code is determined; the target processing operation includes at least one of the following: returning a prompt message, triggering enhanced verification.

[0012] Secondly, embodiments of this application provide an account security management system applied to a server; the account security management system includes: a first information acquisition module, a business determination module, a second information acquisition module, a security check module, and a business processing module, wherein,

[0013] The first information acquisition module is used to acquire target session information through a preset database based on the target session credentials for the target user; the target session information includes: first device information, first user information, and first environment information;

[0014] The business determination module is used to determine the target business performed by the target user; the target business includes any one of the following: credit application business, transaction business, and repayment business.

[0015] The second information acquisition module is used to acquire the target user information of the target user; the target user information includes: second device information, second user information, and second environment information;

[0016] The security check module is used to perform a security check on the target service based on the target session information and the target user information, and obtain the security check result.

[0017] The business processing module is used to execute the target business if the security check result is passed;

[0018] The business processing module is also used to generate a session exception code and determine the target processing operation corresponding to the session exception code if the security check result is unsuccessful; the target processing operation includes at least one of the following: returning a prompt message or triggering enhanced verification.

[0019] Thirdly, embodiments of this application provide an electronic device, including: a processor, a memory, a communication interface, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the processor, and the programs include instructions for performing the steps in the first aspect of embodiments of this application.

[0020] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program for electronic data interchange, wherein the computer program causes a computer to perform some or all of the steps described in the first aspect of embodiments of this application.

[0021] Fifthly, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps described in the first aspect of embodiments of this application. The computer program product may be a software installation package.

[0022] It can be seen that the embodiments of this application have the following beneficial effects:

[0023] By implementing the embodiments of this application, target session information is obtained from a preset database based on the target session credentials for the target user; the target service performed by the target user is determined; target user information of the target user is obtained; a security check is performed on the target service based on the target session information and the target user information to obtain a security check result; if the security check result is passed, the target service is executed; if the security check result is failed, a session exception code is generated, and the target processing operation corresponding to the session exception code is determined. It is evident that by linking and verifying session information and service operation information, abnormal account states can be accurately identified, effectively preventing the security risk of session hijacking. Attached Figure Description

[0024] To more clearly illustrate the technical solutions in the embodiments of this application or the background art, the accompanying drawings used in the embodiments of this application or the background art will be described below.

[0025] Figure 1 This is a flowchart illustrating an account security management method provided in an embodiment of this application;

[0026] Figure 2 This is a system architecture diagram of a server provided in an embodiment of this application;

[0027] Figure 3 This is a schematic diagram of a scenario for a re-login prompt message provided in an embodiment of this application;

[0028] Figure 4 This is a schematic diagram illustrating a scenario for applying for credit authorization, as provided in an embodiment of this application.

[0029] Figure 5 This is a schematic diagram of a transaction business scenario provided in an embodiment of this application;

[0030] Figure 6 This is a schematic diagram illustrating a repayment service scenario provided in an embodiment of this application;

[0031] Figure 7 This is a schematic diagram of the structure of an account security management system provided in an embodiment of this application;

[0032] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0033] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0034] The terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0035] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0036] The following describes the relevant content, concepts, meanings, technical issues, technical solutions, and beneficial effects involved in the embodiments of this application.

[0037] Please see Figure 1 , Figure 1 This is a flowchart illustrating an account security management method provided in an embodiment of this application. The method is applied to a server and includes, but is not limited to, the following steps:

[0038] S101. Obtain target session information from a preset database based on the target session credentials for the target user.

[0039] In this embodiment of the application, the server includes: a business system and a risk control system.

[0040] Please see Figure 2 , Figure 2This is a system architecture diagram of a server provided in an embodiment of this application. As shown in the figure, the business system serves as the direct interface for user interaction, responsible for handling various specific business requests, such as credit applications, transactions, and repayments. For example, in the credit application process, the business system can receive real-name information such as ID card and name entered by the user on the front end and trigger pre-processing operations such as card binding and liveness authentication; in the transaction process, the business system responds to loan or consumption requests and coordinates the verification process of payment vouchers; in the repayment process, the business system connects to repayment channels such as bank cards and Alipay to handle the specific operations of fund deduction. The risk control system is mainly responsible for risk detection and decision control, and it conducts risk assessment by receiving risk control event information (such as login device information, transaction environment information, etc.) sent by the business system.

[0041] In this embodiment of the application, the preset database refers to a database that is pre-configured for storing session information. This database usually adopts a distributed storage architecture or caching technology (such as Redis) to ensure that session information can be read quickly and reliably in a multi-server deployment environment, so as to meet the high concurrency processing requirements of the account security management system.

[0042] In a specific embodiment, the target user can send a target session credential through a terminal device connected to the server. After receiving the target session credential, the server can retrieve the target session information from a preset database based on the target session credential for the target user. The target session credential refers to a key identifier used to identify a user's session, which can be information such as a session ID or cookie generated during the user login process. Its function is to uniquely determine a user's session state.

[0043] In this embodiment, the target session information includes: first device information, first user information, and first environment information. The first device information includes characteristics of the device used by the target user during login, such as the device's unique identifier (e.g., IMEI, MAC address), device model, and operating system version. The first user information includes the target user's identity attributes, such as the customer ID assigned after real-name authentication, the user's real-name authentication status, and the user's basic registration information (e.g., mobile phone number, user ID). The first environment information includes the network environment and other relevant environmental characteristics of the target user during login, such as the IP address, the city information corresponding to the IP address, the login timestamp, and the login channel (e.g., APP, H5, mini-program). It should be noted that different login channels have varying device information stability (e.g., APP channel device information is relatively stable, while mini-program channel may have mixed device information). Therefore, different verification strategies must be used for different login channels in subsequent verification.

[0044] As can be seen, by obtaining the target session information, a baseline information file of the user login can be established on the server side to ensure that the device, user and environment baseline information at the time of login can be quickly retrieved when the user performs subsequent business operations.

[0045] Optionally, before obtaining the target session information from a preset database based on the target session credentials for the target user, the following steps are further included:

[0046] A101. Obtain the login user information of the target user; the login user information includes: third device information, third user information, and third environment information;

[0047] A102. Generate a corresponding session credential based on the logged-in user information to obtain the target session credential;

[0048] A103. Determine whether the target user's session information exists in the preset database based on the target session credentials;

[0049] A104. If the preset database does not contain session information corresponding to the target user, then a key-value pair is determined based on the target session credentials and the login user information, and a preset expiration time is set for the key-value pair; the preset expiration time is used to characterize the time the key-value pair exists in the preset database.

[0050] A105. Store the key-value pair in the preset database and return the target session credential to the target user.

[0051] In a specific embodiment, before the server performs the operation of obtaining target session information based on the target session credentials, a pre-process of generating and storing session credentials needs to be completed. First, the login user information of the target user can be obtained, including: third-party device information (such as unique device identifier, device model, operating system version, etc.), third-party user information (including mobile phone number, user ID, real-name authenticated customer ID, etc.), and third-party environment information (such as login IP address, IP corresponding city, login timestamp, login channel, etc.).

[0052] Next, a corresponding session credential, or target session credential, is generated based on the logged-in user information. This generation process typically uses encryption algorithms (such as hash algorithms or token generation mechanisms) to encode key feature values ​​from device, user, and environment information, forming a unique string (such as Session ID or Cookie) that identifies the login session. This credential must be unique and secure, accurately corresponding to a specific user's login session while preventing malicious forgery or tampering.

[0053] A preset database can be queried based on the target session credentials to determine if session information corresponding to the target user exists. If no corresponding session information is found in the preset database, it indicates that the user is logging in for the first time or the session has expired, and a storage operation needs to be performed. A key-value pair can be determined for storage based on the target session credentials and logged-in user information. The key is typically the target session credentials, and the value contains core fields from the logged-in user information (such as device information, user information, and environment information). Simultaneously, a preset expiration time can be set for the stored key-value pair. This time is set based on a balance between user behavior habits and security risks. For example, the preset expiration time can be set to 1 hour, which ensures that normal users maintain session validity within a reasonable operating time while reducing the risk of session credentials being stolen due to long-term retention through an automatic expiration mechanism.

[0054] Finally, the system stores the key-value pairs in the preset database and returns the target session credential to the target user. When performing business operations in the future, the target user needs to carry the target session credential so that the server can identify the session identity.

[0055] It is evident that by effectively managing session state, the continuity of user operations within the session period is ensured, while the risk of session credentials being abused is reduced through expiration duration control and secure storage strategies.

[0056] S102. Determine the target service performed by the target user.

[0057] In this embodiment of the application, determining the target business performed by the target user can enable scenario-based differentiated security control, so that when the target user initiates a business operation request through session credentials, the server can clearly identify the specific business type and perform targeted security checks.

[0058] In a specific embodiment, the target business performed by the target user can be determined, wherein the target business includes any one of the following: credit application business, transaction business, and repayment business.

[0059] The credit application service mainly refers to the identity verification and qualification review operations performed by the target user, such as card binding, liveness detection, and facial recognition. In this service scenario, the user needs to enter information such as ID card number, name, and bank card number on the front end. The server can determine the service attribute by using the service type identifier in the interface request (such as card binding event, facial recognition pre-event, etc.).

[0060] Transaction operations mainly refer to the actions of target users in withdrawing or consuming funds, including scenarios such as cash withdrawal and consumption payment. When a user clicks the loan button or makes a consumption transaction, the server can determine whether it is a transaction operation through parameters such as the functional module identifier (e.g., loan / transaction interface call) and the transaction type field (e.g., cash withdrawal, consumption) in the transaction request.

[0061] Repayment services mainly refer to the actions taken by target users to repay their debts, including different methods such as bank card repayment and third-party app repayment. When a target user clicks the repayment button, the server can identify the service type by using information such as the service type parameter (e.g., repayment) and the repayment method field (e.g., bank card, third-party app) in the repayment request.

[0062] As can be seen, by identifying the target user's target business, the server can implement differentiated security inspection strategies and anomaly handling mechanisms based on the risk characteristics and security requirements of different business scenarios. For example, credit application business involves the submission of user real-name information, so the focus can be on preventing the risk of information misuse due to session errors; transaction business, because it is directly related to fund flow, requires strengthened verification requirements for payment vouchers; and repayment business, due to the special nature of third-party payment channels, requires additional protective measures such as dynamic code verification. This scenario-based management model ensures account security while minimizing interference with normal user business operations, achieving a balance between security and user experience.

[0063] S103. Obtain the target user information of the target user.

[0064] In this embodiment, target user information refers to the transaction user information uploaded to the server when a target user performs a transaction. It differs in function from target session information and login user information. Target session information is data stored in a pre-set database on the server after a user logs in; it is baseline data that has undergone security verification. Login user information is data initially uploaded to the server upon user login, stored as target session information after system verification, and is the initial data source. Target user information, as real-time data during a transaction, is subject to security risks such as network hijacking and therefore needs to be compared and verified with target session information to identify abnormal operations. Target session information, login user information, and target user information all include device information, user information, and environmental information.

[0065] In a specific embodiment, after a target user initiates a target service request, the target user's terminal device can upload transaction user information, i.e., target user information, to the server through an encrypted channel. This target user information includes fields such as: second device information (e.g., unique device identifier, device model, operating system version, etc.), second user information (e.g., mobile phone number, user ID, customer ID, real-name registration status), and second environment information (e.g., login IP address, IP-corresponding city, login timestamp, login channel, etc.). Because transaction data may be maliciously tampered with during network transmission (e.g., forging transaction user information in a session hijacking attack), the server must first ensure the integrity of the target user information through mechanisms such as digital signature verification and encrypted data transmission, and then perform a multi-dimensional comparison with the target session information stored in a preset database.

[0066] For example, in a transaction scenario, when a target user performs a cash withdrawal operation, the server first retrieves the target session information (such as device A information and customer ID1 at the time of login) from a preset database, and simultaneously obtains the target user information uploaded during the transaction (such as device B information and customer ID2). If customer ID2 is inconsistent with customer ID1 and it is not a loan repayment scenario, the system can directly determine that there is a risk of account theft; if the device ID changes from A to B and the device model is significantly different, there may be a risk of device hijacking; if the IP address changes suddenly and there is no reasonable movement trajectory, combined with environmental information, it can be determined as an abnormal login.

[0067] Furthermore, the comparison strategies for target user information and target session information need to be differentiated based on the risk characteristics of different business scenarios. For example, in credit application business, since the target user has not yet completed real-name authentication, the system can relax the detection conditions for device and IP changes, only judging anomalies when multiple devices and IPs change; while in transaction business, since it directly involves the flow of funds, strict consistency verification must be implemented, and even non-exempt rules may be set for dynamic code verification. This scenario-based verification mechanism not only considers the security risk of target user information being hijacked, but also achieves accurate risk identification through benchmark data comparison, avoiding excessive interference with normal user operations.

[0068] It is evident that by clearly distinguishing between target user information, target session information, and login user information, and by constructing a real-time verification mechanism based on trusted benchmark data, the risk of account theft caused by the hijacking of transaction user information can be effectively prevented.

[0069] S104. Perform a security check on the target service based on the target session information and the target user information to obtain the security check result.

[0070] In a specific embodiment, security checks can be performed on the target business based on the target session information and the target user information to obtain security check results. Specifically, by comparing and analyzing the baseline data (target session information) when the target user logs in with the real-time data (target user information) when the transaction takes place in multiple dimensions, and combining the risk characteristics of the target business, accurate identification of account anomalies can be achieved. It can perform verification from aspects such as user identity consistency, device environment stability, and network environment compliance, and implement differentiated check strategies according to the business type (credit application, transaction, repayment).

[0071] It is evident that by conducting multi-dimensional security checks on target session information and target user information, and implementing differentiated verification strategies based on the risk characteristics of the target business, security risks such as device impersonation, identity forgery, and abnormal network environment can be accurately identified. This provides real-time dynamic protection for account security, effectively blocks illegal transactions, and reduces interference with normal users, achieving a balance between security and user experience.

[0072] Optionally, when the target service is the credit application service; the step of performing a security check on the target service based on the target session information and the target user information to obtain a security check result specifically includes the following steps:

[0073] A401. Perform a first check on the target user based on the target user information to obtain a first check result; the first check includes any one of the following: bank card association check, liveness authentication;

[0074] A402. If the first inspection result is "fail", then the security inspection result is determined to be "fail".

[0075] A403. If the first check result is passed, then determine whether the target session information and the target user information meet the first preset condition; the first preset condition is used to indicate that the device ID in the target session information is the same as the device ID in the target user information.

[0076] A404. If the target session information and the target user information meet the first preset condition, then the security check result is determined to be passed.

[0077] A405. If the target session information and the target user information do not meet the first preset condition, then determine whether the target session information and the target user information meet the second preset condition; the second preset condition is used to indicate that the login IP in the target session information is the same as the login IP in the target user information.

[0078] A406. If the target session information and the target user information meet the second preset condition, then the security check result is determined to be passed;

[0079] A407. If the target session information and the target user information do not meet the second preset condition, the security check result is determined to be unsuccessful.

[0080] In a specific embodiment, when the target business is a credit application, a first check can be performed on the target user based on the target user information to obtain a first check result. The first check includes any one of the following: bank card association check and liveness authentication. The bank card association check mainly verifies the consistency between the bank card information entered by the user and the real-name information, including verification of fields such as cardholder name, ID number, and bank card number. Liveness authentication uses facial recognition technology to determine whether the operating entity is a genuine user to prevent identity theft. If the first check fails, such as bank card information verification failure or liveness detection failure, the security check result is directly determined to be unsuccessful, and the business process is terminated.

[0081] If the first check passes, the system will further determine whether the target session information and target user information meet the first preset condition. The first preset condition requires that the device ID in the target session information and the device ID in the target user information be the same to ensure that the user's device has not changed during the credit application process. When the device IDs are the same, it indicates that the current operating environment is consistent with the baseline environment at the time of login, and the security check is considered passed, allowing the credit application to continue. If the device IDs are inconsistent, such as in an H5 scenario where the device ID changes, this does not necessarily mean the transaction environment is insecure. Therefore, the system will further determine whether the target session information and target user information meet the second preset condition. The second preset condition requires that the login IP in the target session information and the login IP in the target user information be the same. When the login IPs are the same, the security check is considered passed; otherwise, the security check is considered failed only when the login IPs are inconsistent.

[0082] It is evident that by implementing a dual-check mechanism of identity verification and environment consistency verification in the credit application process, the risk of information misuse due to session errors or device hijacking can be effectively prevented. While ensuring the authenticity of user identity, the stability of the operating environment is also guaranteed, providing reliable technical support for the secure operation of credit services.

[0083] Optionally, when the target service is the transaction service, or the target service is the repayment service; the step of performing a security check on the target service based on the target session information and the target user information to obtain a security check result specifically includes the following steps:

[0084] B401. Determine whether the target user is registered with their real name based on the target user information;

[0085] B402. If the target user is not registered with their real name, return a real-name registration prompt and re-execute the step of determining the target user's target business; the real-name registration prompt is used to prompt the target user to apply for credit.

[0086] B403. If the target user has been registered with their real name, then determine whether the target session information and the target user information meet the third preset condition; the third preset condition is used to indicate that the customer ID in the target session information is the same as the customer ID in the target user information.

[0087] B404. If the target session information and the target user information satisfy the third preset condition, then determine whether the target session information and the target user information satisfy the fourth preset condition; the fourth preset condition is used to indicate that the device ID in the target session information is the same as the device ID in the target user information, or the device model in the target session information is the same as the device model in the target user information.

[0088] B405. If the target session information and the target user information meet the fourth preset condition, then the security check result is determined to be passed.

[0089] B406. If the target session information and the target user information do not meet the fourth preset condition, then the security check result is determined to be unsuccessful.

[0090] B407. If the target session information and the target user information do not meet the third preset condition, then the security check result is determined to be unsuccessful.

[0091] In a specific embodiment, when the target business is a transaction business or a repayment business, the system can first determine whether the target user has completed real-name authentication based on the target user information. If the target user has not completed real-name authentication, the system will return a real-name authentication prompt, which guides the user to apply for credit services to complete identity verification. Then, the steps to determine the target business are re-executed to ensure that the user performs transactions or repayments under a real-name status.

[0092] If the target user has already registered with their real name, a multi-level verification process for identity and device environment is initiated. First, it checks whether the target session information and target user information meet the third preset condition: the customer ID in the session information is the same as the customer ID in the user information. If the customer IDs match, it continues to check whether the fourth preset condition is met: either the session device ID is the same as the user device ID, or the session device model is the same as the user device model. If the device IDs match or the device models match, the security check is considered passed, and the target service is allowed to proceed; otherwise, the security check is considered failed. Specifically, when the customer IDs do not match, the security check can be directly deemed failed. If the customer IDs match, it continues to check whether the device ID or device model matches. If both the device ID and device model do not match, an exception handling mechanism is triggered, blocking the service process.

[0093] It is evident that by implementing a layered verification process in transaction and repayment operations, risks such as identity theft and device hijacking of real-name users can be effectively prevented. This provides a rigorous security system for business scenarios involving fund flows, ensuring transaction security while guaranteeing the smooth execution of normal business processes.

[0094] Optionally, when the target business is a repayment business, the repayment channel corresponding to the repayment business is a third-party APP scenario, and the target session information and the target user information do not meet the fourth preset condition, the following steps are further included:

[0095] C401. Determine whether the target session information and the target user information satisfy a preset fifth condition; the preset fifth condition is used to indicate that the location of the IP in the target session information is the same as the location of the IP in the target user information.

[0096] C402. If the target session information and the target user information meet the preset fifth condition, the security check is determined to be passed; if the target session information and the target user information do not meet the preset fifth condition, the security check result is determined to be failed.

[0097] In a specific embodiment, when the target business is a repayment business and the repayment channel is a third-party APP, after the target session information and target user information do not meet the fourth preset condition, a network environment consistency check can be further implemented. First, it is determined whether the target session information and target user information meet the preset fifth condition, that is, the location of the session IP is the same as the location of the transaction IP. The location of the IP can be obtained through IP address database resolution.

[0098] If the IP addresses match, it indicates that the user's network environment has not changed abnormally, the security check is passed, and the repayment process can continue. If the IP addresses do not match, it indicates an abnormal network environment, the security check fails, and the exception handling mechanism is triggered. This additional verification step is designed specifically for third-party app repayment scenarios. Since it is impossible to directly intercept the verification process of the third-party payment platform in this scenario, the consistency verification of IP addresses is needed to further reduce the risk of session hijacking.

[0099] It is evident that by adding IP address consistency verification in third-party app repayment scenarios, the blind spots of third-party channels are effectively filled, the security of repayment services in complex network environments is improved, and more comprehensive technical protection is provided for user fund security.

[0100] S105. If the security check result is passed, then the target service is executed.

[0101] In a specific embodiment, after completing the security check on the target service, if the security check result is passed, it indicates that no abnormal risk has been detected in the target service operation, and it belongs to the normal operation behavior of a legitimate user. At this time, the system will allow the execution of the target service.

[0102] Specifically, in credit application scenarios, if the security check passes, the system will continue with the real-name authentication process, such as card binding and liveness verification, to complete the verification of the user's identity and grant the user the corresponding credit limit. In transaction scenarios, after the security check passes, the system will execute operations such as cash withdrawal and consumption payment according to the transaction type, and process fund transfers according to business rules, such as deducting account balances and completing payment settlements. For repayment transactions, after the security check passes, the system will initiate a fund deduction instruction according to the repayment method to complete the debt repayment operation and update the repayment status of the user's account.

[0103] In addition, when executing target business, complete operation logs can be recorded, including information such as business type, operation time, participating entities, and operation content, so as to facilitate subsequent business traceability, audit verification, and risk analysis. These log data can provide data support for business operations and also provide a reference for transaction system optimization and security strategy adjustment.

[0104] S106. If the security check result is unsuccessful, a session exception code is generated, and the target processing operation corresponding to the session exception code is determined.

[0105] In a specific embodiment, when the security check result is unsuccessful, a session exception code can be generated and the corresponding target processing operation can be determined. If the current business operation is determined to have abnormal risks (such as session hijacking, device impersonation, IP cross-regional change, etc.) through multi-dimensional verification (such as user identity, device information, network environment, etc.), a specific session exception code (such as RCSFS444) and the corresponding target processing operation will be generated. The target processing operation includes at least one of the following: returning prompt information and triggering enhanced verification.

[0106] The implementation strategies for target processing operations vary depending on the business scenario. For example, in credit application business, which involves the submission of real-name information, if the security check fails, the system mainly guides the user to log in again by returning a prompt message to avoid unauthorized information entry. Transaction business is directly related to fund flow and has the highest risk level. In addition to returning a prompt message, it usually triggers a combination verification of the transaction code and the transaction password, and the transaction code cannot be exempted. In repayment business, there are blind spots in the interception of third-party payment channels. When the security check fails, the system will forcibly verify the transaction code to ensure that the fund deduction operation is initiated by a legitimate user.

[0107] As can be seen, by generating session exception codes and executing corresponding target processing operations, the system can implement precise and graded handling of detected account anomaly risks, thus ensuring account security.

[0108] Optionally, the target processing operation includes: returning the prompt information; the target processing operation corresponding to the session exception code specifically includes the following steps:

[0109] A601. Generate a first login re-login prompt message and return the first login re-login prompt message to the target user; the first login re-login prompt message is used to instruct the target user to log in again.

[0110] A602. Delete the target session information through the preset database.

[0111] In a specific embodiment, when the target service is a credit application service, the target processing operation includes: returning a prompt message. Specifically, a first re-login prompt message can be generated and returned to the target user, whereby the first re-login prompt message is used to instruct the target user to log in again. Next, the target session information can be deleted through a preset database. By removing the stored session key-value pairs, it is ensured that the abnormal session can no longer be used, preventing malicious users from launching attacks using expired session credentials.

[0112] Please see Figure 3 , Figure 3 This is a schematic diagram illustrating a scenario for a re-login prompt message provided in an embodiment of this application. The diagram shows a credit application page. When a target user enters this page, the message "Please confirm the following information" is displayed to remind the target user to confirm their bank card information (such as cardholder, card number, mobile phone number, etc.). After confirming that the information is correct, the target user can click "Next" to proceed with a security check. If the security check passes, the user can submit feedback via the customer icon in the upper right corner of the credit application page. If the security check fails during the credit application process (e.g., account risk is detected, such as abnormal conversation or questionable identity verification), a re-login prompt message generation process is triggered. First, a first re-login prompt message (such as "The current account is at risk; please log in again before proceeding!") is generated and displayed to the target user, informing them that they need to log in again due to account risk. At the same time, by using a pre-set database (such as a database that stores session information), the target session information is deleted, and the current session data that may pose a risk is cleaned up, allowing the user to log in again to establish a new and secure session connection. This ensures that subsequent business operations are carried out in a secure environment, prevents risks such as unauthorized use of accounts, and maintains account security and business order.

[0113] It is evident that by prompting users to log in again and deleting session information, abnormal session states can be terminated in a timely manner, effectively preventing the risk of session hijacking. At the same time, users are prompted to log in again to update their session credentials, establishing a secure session environment for subsequent business operations. This approach enables rapid handling of abnormal sessions while ensuring account security.

[0114] Optionally, when the target service is the transaction service, or the target service is the repayment service, and the security check result is a failure, the target processing operation includes: returning a prompt message and triggering enhanced verification; the target processing operation corresponding to the session exception code specifically includes the following steps:

[0115] B601. Determine the first verification method; the first verification method includes at least one of the following: transaction password and dynamic verification code, liveness authentication, video verification, and fingerprint verification;

[0116] B602. Obtain the verification result of the target user based on the first verification method to obtain the first verification result;

[0117] B603. If the first verification result is successful, the target service is executed; if the first verification result is unsuccessful, a second login re-login prompt is generated and returned to the target user; the second login re-login prompt is used to instruct the target user to log in again.

[0118] In a specific embodiment, when the target business is a transaction business or a repayment business, and the security check result is unsuccessful, the target processing operation may include: returning a prompt message and triggering enhanced verification. First, a first verification method is determined, which includes at least one of the following: transaction password and dynamic verification code, liveness authentication, video verification, and fingerprint verification. Next, the result of the target user's verification based on the first verification method is obtained, resulting in a first verification result. If the first verification result is successful, it indicates that the user's identity and operation are legitimate, and the target business can be executed, ensuring the continuity of the business process. If the first verification result is unsuccessful, it indicates that the current user verification does not meet the security standard. In this case, a second re-login prompt message is generated and returned to the target user, guiding them to log in again. By rebuilding the session, potential risks are eliminated, ensuring that subsequent business operations are carried out in a secure environment.

[0119] It is evident that by adapting to risk scenarios through multiple verification methods, accurately identifying risks, and making business decisions based on verification results, legitimate operations are ensured, anomalies are blocked, and a re-login is triggered to reset the session, cutting off the transmission of risks. This builds layered protection for financial transactions, balances security and user experience, and effectively improves the security of transaction operations.

[0120] Please see Figure 4 , Figure 4 This is a schematic diagram of a credit application scenario provided by an embodiment of this application. As shown in the figure, in the credit application scenario, the user triggers a pre-check operation for card binding / face assessment (step 1.0) and transmits the request to the business system. After receiving the request, the business system forwards the card binding / face assessment pre-check event to the risk control system (step 1.1). After receiving the event, the risk control system performs an account security check (step 1.2), assesses the account security status based on preset risk rules, and determines whether there are any abnormal risks, such as identity theft or device malfunction. After completing the check, the risk control system returns the check result to the business system (step 1.3), and the business system then returns the check result to the user (step 1.4). If the check finds an account abnormality, a re-login process is triggered (step 1.5), requiring the user to re-verify their identity, thereby blocking abnormal operations and ensuring account security.

[0121] Please see Figure 5 , Figure 5 This is a schematic diagram of a transaction business scenario provided by an embodiment of this application. As shown in the figure, in the transaction business scenario, the user clicks the repayment operation (step 1.0). This operation triggers the business system to perform a pre-repayment check (step 1.1). The business system then initiates an environment check request to the risk control system (step 1.2). Based on the environment check, the risk control system simultaneously conducts an account security check (step 1.3), comprehensively assessing the transaction risk by integrating multi-dimensional data such as the user's device environment and account status. After completing the check, the risk control system returns the check results to the business system (step 1.4). If there is an account anomaly, the business system triggers the dynamic code verification process (step 1.5), sending and verifying the dynamic code to the user (step 1.6), that is, sending and verifying the dynamic verification code, strengthening identity verification through secondary verification.

[0122] Once verification is successful or the initial check shows no abnormalities, the user can submit a loan / transaction (step 1.7). The business system pushes the withdrawal / transaction event to the risk control system (step 1.8). The risk control system performs a risk check based on preset transaction check rules (step 1.9), checking the transaction amount, fund flow, etc., and then returns the check results to the business system (step 1.10). The business system executes the withdrawal / transaction based on the results (step 1.11) and returns the withdrawal transaction result to the user (step 1.12).

[0123] Please see Figure 6 , Figure 6This is a schematic diagram of a repayment business scenario provided in an embodiment of this application. As shown in the figure, in the repayment business scenario, the user clicks the repayment operation (step 1.0), triggering the business system to perform a pre-repayment check (step 1.1). The business system then initiates an environment check request to the risk control system (step 1.2). While conducting the environment check, the risk control system simultaneously performs an account security check (step 1.3) to conduct a preliminary assessment of the security of the repayment operation. After completing the check, the risk control system returns the result to the business system (step 1.4). If there is an account anomaly, the business system will trigger a dynamic code verification process (step 1.5), sending a dynamic code to the user and verifying the dynamic code (step 1.6). Through a two-factor authentication mechanism, the legitimacy of the operating entity is strengthened.

[0124] Once verification is successful or the initial check shows no abnormalities, the user submits a repayment request (step 1.7). The business system pushes the repayment event to the risk control system (step 1.8). The risk control system performs a repayment security check based on the characteristics of the repayment transaction (step 1.9), focusing on risk checks regarding the source of repayment funds, the status of the repayment account, and the matching degree between the repayment amount and the outstanding debt. The check results are then returned to the business system (step 1.10). The business system executes the repayment operation based on the results (step 1.11) and returns the repayment result to the user (step 1.12).

[0125] In summary, by implementing the embodiments of this application, target session information can be obtained from a preset database based on the target session credentials for the target user; the target service performed by the target user can be determined; target user information of the target user can be obtained; a security check can be performed on the target service based on the target session information and the target user information to obtain a security check result; if the security check result is passed, the target service is executed; if the security check result is failed, a session exception code is generated, and the target processing operation corresponding to the session exception code is determined. It is evident that by linking and verifying session information and service operation information, abnormal account states can be accurately identified, effectively preventing the security risk of session hijacking.

[0126] Please see Figure 7 , Figure 7 This is a schematic diagram of the structure of an account security management system provided in an embodiment of this application. The account security management system 700 includes: a first information acquisition module 701, a business determination module 702, a second information acquisition module 703, a security check module 704, and a business processing module 705, wherein...

[0127] The first information acquisition module 701 is used to acquire target session information through a preset database based on the target session credentials for the target user; the target session information includes: first device information, first user information, and first environment information;

[0128] The business determination module 702 is used to determine the target business performed by the target user; the target business includes any one of the following: credit application business, transaction business, repayment business;

[0129] The second information acquisition module 703 is used to acquire the target user information of the target user; the target user information includes: second device information, second user information, and second environment information;

[0130] The security check module 704 is used to perform a security check on the target service based on the target session information and the target user information, and obtain a security check result.

[0131] The business processing module 705 is used to execute the target business if the security check result is passed;

[0132] The business processing module 705 is further configured to generate a session exception code and determine the target processing operation corresponding to the session exception code if the security check result is unsuccessful; the target processing operation includes at least one of the following: returning a prompt message or triggering enhanced verification.

[0133] Optionally, before retrieving target session information from a preset database based on target session credentials for the target user, the account security management system 700 is further configured to:

[0134] Obtain the login user information of the target user; the login user information includes: third device information, third user information, and third environment information;

[0135] Generate a corresponding session credential based on the logged-in user information to obtain the target session credential;

[0136] Based on the target session credentials, determine whether the preset database contains session information corresponding to the target user;

[0137] If the preset database does not contain session information corresponding to the target user, then a key-value pair is determined based on the target session credentials and the login user information, and a preset expiration time is set for the key-value pair; the preset expiration time is used to characterize the time the key-value pair exists in the preset database.

[0138] The key-value pair is stored in the preset database, and the target session credential is returned to the target user.

[0139] Optionally, when the target service is the credit application service; in the process of performing a security check on the target service based on the target session information and the target user information to obtain a security check result, the security check module 704 is further specifically used for:

[0140] A first check is performed on the target user based on the target user information to obtain a first check result; the first check includes any one of the following: bank card association check, liveness authentication;

[0141] If the first check result is "fail", then the security check result is determined to be "fail".

[0142] If the first check result is passed, then it is determined whether the target session information and the target user information meet the first preset condition; the first preset condition is used to indicate that the device ID in the target session information is the same as the device ID in the target user information;

[0143] If the target session information and the target user information meet the first preset condition, then the security check result is determined to be passed;

[0144] If the target session information and the target user information do not meet the first preset condition, then it is determined whether the target session information and the target user information meet the second preset condition; the second preset condition is used to indicate that the login IP in the target session information is the same as the login IP in the target user information.

[0145] If the target session information and the target user information meet the second preset condition, then the security check result is determined to be passed;

[0146] If the target session information and the target user information do not meet the second preset condition, the security check result is determined to be unsuccessful.

[0147] Optionally, the target processing operation includes: the return prompt information; in terms of determining the target processing operation corresponding to the session exception code, the service processing module 705 is further specifically used for:

[0148] A first login re-login prompt message is generated and returned to the target user; the first login re-login prompt message is used to instruct the target user to log in again;

[0149] The target session information is deleted from the preset database.

[0150] Optionally, when the target service is the transaction service, or the target service is the repayment service; in the process of performing a security check on the target service based on the target session information and the target user information to obtain a security check result, the security check module 704 is further specifically used for:

[0151] Determine whether the target user is registered with their real name based on the target user information;

[0152] If the target user is not registered with their real name, a real-name registration prompt is returned, and the step of determining the target user's target business is re-executed; the real-name registration prompt is used to prompt the target user to apply for credit.

[0153] If the target user has been registered with their real name, then it is determined whether the target session information and the target user information meet the third preset condition; the third preset condition is used to indicate that the customer ID in the target session information is the same as the customer ID in the target user information.

[0154] If the target session information and the target user information satisfy the third preset condition, then it is determined whether the target session information and the target user information satisfy the fourth preset condition; the fourth preset condition is used to indicate that the device ID in the target session information is the same as the device ID in the target user information, or that the device model in the target session information is the same as the device model in the target user information.

[0155] If the target session information and the target user information meet the fourth preset condition, then the security check result is determined to be passed;

[0156] If the target session information and the target user information do not meet the fourth preset condition, then the security check result is determined to be unsuccessful.

[0157] If the target session information and the target user information do not meet the third preset condition, then the security check result is determined to be unsuccessful.

[0158] Optionally, when the target business is a repayment business, the repayment channel corresponding to the repayment business is a third-party APP scenario, and the target session information and the target user information do not meet the fourth preset condition, the security check module 704 is further specifically used for:

[0159] Determine whether the target session information and the target user information meet a preset fifth condition; the preset fifth condition is used to indicate that the location of the IP address in the target session information is the same as the location of the IP address in the target user information.

[0160] If the target session information and the target user information meet the preset fifth condition, the security check is determined to be passed; if the target session information and the target user information do not meet the preset fifth condition, the security check result is determined to be failed.

[0161] Optionally, when the target service is the transaction service, or the target service is the repayment service, and the security check result is a failure, the target processing operation includes: returning a prompt message and triggering enhanced verification; regarding the target processing operation corresponding to the session exception code, the service processing module 705 is further specifically used for:

[0162] A first verification method is determined; the first verification method includes at least one of the following: transaction password and dynamic verification code, liveness authentication, video verification, and fingerprint verification.

[0163] Obtain the verification result of the target user based on the first verification method to obtain the first verification result;

[0164] If the first verification result is successful, the target service is executed; if the first verification result is unsuccessful, a second login re-login prompt is generated and returned to the target user; the second login re-login prompt is used to instruct the target user to log in again.

[0165] The account security management system 700 described in this application can obtain target session information from a preset database based on target session credentials for a target user; determine the target business being performed by the target user; obtain target user information for the target user; perform a security check on the target business based on the target session information and the target user information, and obtain a security check result; if the security check result is passed, the target business is executed; if the security check result is failed, a session exception code is generated, and the target processing operation corresponding to the session exception code is determined. Therefore, by linking and verifying session information and business operation information, abnormal account states can be accurately identified, effectively preventing the security risk of session hijacking.

[0166] Please see Figure 8 , Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. The electronic device may include a processor, a memory, a communication interface, and one or more programs. The processor, memory, and communication interface can be interconnected via a bus. The one or more programs are stored in the memory and configured to be executed by the processor. In this embodiment, the programs include instructions for performing the following steps:

[0167] Target session information is obtained from a preset database based on the target session credentials for the target user; the target session information includes: first device information, first user information, and first environment information;

[0168] Determine the target business conducted by the target user; the target business includes any one of the following: credit application business, transaction business, repayment business;

[0169] Obtain the target user information of the target user; the target user information includes: second device information, second user information, and second environment information;

[0170] Based on the target session information and the target user information, a security check is performed on the target service to obtain the security check result;

[0171] If the security check is passed, then the target service is executed;

[0172] If the security check fails, a session exception code is generated, and the target processing operation corresponding to the session exception code is determined; the target processing operation includes at least one of the following: returning a prompt message, triggering enhanced verification.

[0173] The electronic device described in this application can obtain target session information from a preset database based on target session credentials for a target user; determine the target service being performed by the target user; obtain target user information for the target user; perform a security check on the target service based on the target session information and the target user information, and obtain a security check result; if the security check result is passed, the target service is executed; if the security check result is failed, a session exception code is generated, and the target processing operation corresponding to the session exception code is determined. Therefore, by linking and verifying session information and service operation information, abnormal account states can be accurately identified, effectively preventing the security risk of session hijacking.

[0174] This application also provides a computer-readable storage medium storing a computer program for electronic data interchange, which causes a computer to perform some or all of the steps of any of the methods described in the above method embodiments, wherein the computer includes an electronic device.

[0175] This application also provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of any of the methods described in the above method embodiments. The computer program product may be a software installation package, and the computer may include an electronic device.

[0176] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.

[0177] The steps of the methods or algorithms described in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in RAM, flash memory, ROM, EPROM, electrically erasable programmable read-only memory (EEPROM), registers, hard disk, portable hard disk, read-only optical disk (CD-ROM), or any other form of storage medium well known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Furthermore, the ASIC can reside in a terminal device or management device. Alternatively, the processor and storage medium can exist as discrete components in the terminal device or management device.

[0178] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in the embodiments of this application can be implemented, in whole or in part, by software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0179] The modules / units included in the various devices and products described in the above embodiments can be software modules / units, hardware modules / units, or a combination of both. For example, for devices and products applied to or integrated into a chip, all modules / units can be implemented using hardware methods such as circuits, or at least some modules / units can be implemented using software programs that run on a processor integrated within the chip, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits. For devices and products applied to or integrated into a chip module, all modules / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or different components of the chip module, or at least some modules / units can be implemented using hardware methods such as circuits. The implementation is achieved through a software program that runs on a processor integrated within the chip module. The remaining modules / units (if any) can be implemented using hardware methods such as circuits. For various devices and products applied to or integrated into terminal equipment, each of their modules / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or different components within the terminal equipment. Alternatively, at least some modules / units can be implemented using a software program that runs on a processor integrated within the terminal equipment, while the remaining modules / units (if any) can be implemented using hardware methods such as circuits.

[0180] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the embodiments of this application. It should be understood that the above descriptions are merely specific embodiments of the embodiments of this application and are not intended to limit the protection scope of the embodiments of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solutions of the embodiments of this application should be included within the protection scope of the embodiments of this application.

Claims

1. An account security management method, characterized in that, Applied to a server; the method includes: Target session information is obtained from a preset database based on the target session credentials for the target user; the target session information includes: first device information, first user information, and first environment information; Determine the target business conducted by the target user; the target business includes any one of the following: credit application business, transaction business, repayment business; Obtain the target user information of the target user; the target user information includes: second device information, second user information, and second environment information; Based on the target session information and the target user information, a security check is performed on the target service to obtain the security check result; If the security check is passed, then the target service is executed; If the security check fails, a session exception code is generated, and the target processing operation corresponding to the session exception code is determined; the target processing operation includes at least one of the following: returning a prompt message, triggering enhanced verification.

2. The method as described in claim 1, characterized in that, Before retrieving target session information from a preset database based on target session credentials for the target user, the method further includes: Obtain the login user information of the target user; the login user information includes: third device information, third user information, and third environment information; Generate a corresponding session credential based on the logged-in user information to obtain the target session credential; Based on the target session credentials, determine whether the preset database contains session information corresponding to the target user; If the preset database does not contain session information corresponding to the target user, then a key-value pair is determined based on the target session credentials and the login user information, and a preset expiration time is set for the key-value pair; the preset expiration time is used to characterize the time the key-value pair exists in the preset database. The key-value pair is stored in the preset database, and the target session credential is returned to the target user.

3. The method as described in claim 1 or 2, characterized in that, When the target service is the credit application service; the step of performing a security check on the target service based on the target session information and the target user information to obtain the security check result includes: A first check is performed on the target user based on the target user information to obtain a first check result; the first check includes any one of the following: bank card association check, liveness authentication; If the first check result is "fail", then the security check result is determined to be "fail". If the first check result is passed, then it is determined whether the target session information and the target user information meet the first preset condition; the first preset condition is used to indicate that the device ID in the target session information is the same as the device ID in the target user information; If the target session information and the target user information meet the first preset condition, then the security check result is determined to be passed; If the target session information and the target user information do not meet the first preset condition, then it is determined whether the target session information and the target user information meet the second preset condition; the second preset condition is used to indicate that the login IP in the target session information is the same as the login IP in the target user information. If the target session information and the target user information meet the second preset condition, then the security check result is determined to be passed; If the target session information and the target user information do not meet the second preset condition, the security check result is determined to be unsuccessful.

4. The method as described in claim 3, characterized in that, The target processing operation includes: returning the prompt information; the target processing operation corresponding to the session exception code includes: A first login re-login prompt message is generated and returned to the target user; the first login re-login prompt message is used to instruct the target user to log in again; The target session information is deleted from the preset database.

5. The method as described in claim 1 or 2, characterized in that, When the target service is the transaction service, or the target service is the repayment service; the step of performing a security check on the target service based on the target session information and the target user information to obtain a security check result includes: Determine whether the target user is registered with their real name based on the target user information; If the target user is not registered with their real name, a real-name registration prompt is returned, and the step of determining the target user's target business is re-executed; the real-name registration prompt is used to prompt the target user to apply for credit. If the target user has been registered with their real name, then it is determined whether the target session information and the target user information meet the third preset condition; the third preset condition is used to indicate that the customer ID in the target session information is the same as the customer ID in the target user information. If the target session information and the target user information satisfy the third preset condition, then it is determined whether the target session information and the target user information satisfy the fourth preset condition; the fourth preset condition is used to indicate that the device ID in the target session information is the same as the device ID in the target user information, or that the device model in the target session information is the same as the device model in the target user information. If the target session information and the target user information meet the fourth preset condition, then the security check result is determined to be passed; If the target session information and the target user information do not meet the fourth preset condition, then the security check result is determined to be unsuccessful. If the target session information and the target user information do not meet the third preset condition, then the security check result is determined to be unsuccessful.

6. The method as described in claim 5, characterized in that, When the target business is a repayment business, the repayment channel corresponding to the repayment business is a third-party APP scenario, and the target session information and the target user information do not meet the fourth preset condition, the method further includes: Determine whether the target session information and the target user information meet a preset fifth condition; the preset fifth condition is used to indicate that the location of the IP address in the target session information is the same as the location of the IP address in the target user information. If the target session information and the target user information meet the preset fifth condition, the security check is determined to be passed; if the target session information and the target user information do not meet the preset fifth condition, the security check result is determined to be failed.

7. The method as described in claim 5, characterized in that, When the target service is the transaction service, or the target service is the repayment service, and the security check result is a failure, the target processing operation includes: returning a prompt message and triggering enhanced verification; the target processing operation corresponding to the session exception code includes: A first verification method is determined; the first verification method includes at least one of the following: transaction password and dynamic verification code, liveness authentication, video verification, and fingerprint verification. Obtain the verification result of the target user based on the first verification method to obtain the first verification result; If the first verification result is successful, the target service is executed; if the first verification result is unsuccessful, a second login re-login prompt is generated and returned to the target user; the second login re-login prompt is used to instruct the target user to log in again.

8. An account security management system, characterized in that, Applied to servers; The account security management system includes: a first information acquisition module, a business determination module, a second information acquisition module, a security check module, and a business processing module, wherein... The first information acquisition module is used to acquire target session information through a preset database based on the target session credentials for the target user; the target session information includes: first device information, first user information, and first environment information; The business determination module is used to determine the target business performed by the target user; the target business includes any one of the following: credit application business, transaction business, and repayment business. The second information acquisition module is used to acquire the target user information of the target user; the target user information includes: second device information, second user information, and second environment information; The security check module is used to perform a security check on the target service based on the target session information and the target user information, and obtain the security check result. The business processing module is used to execute the target business if the security check result is passed; The business processing module is also used to generate a session exception code and determine the target processing operation corresponding to the session exception code if the security check result is unsuccessful; the target processing operation includes at least one of the following: returning a prompt message or triggering enhanced verification.

9. An electronic device, characterized in that, include: Processor, memory, communication interface, and one or more programs; The one or more programs are stored in the memory and configured to be executed by the processor, the programs including instructions for performing the steps of the method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, the computer program including program instructions that, when executed by a processor, cause the processor to perform the method as described in any one of claims 1-7.

Images