Transaction implementation method and device, equipment and storage medium
By centralizing user-level permission configuration and transaction verification, the transaction security problem caused by fragmented user permissions is solved, enabling comprehensive and timely permission verification during user transactions and ensuring transaction security.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-10-30
- Publication Date
- 2026-03-27
AI Technical Summary
In business applications, fragmented user permission configurations make it impossible to perform comprehensive verification of user permissions in a timely and effective manner, thus affecting transaction security.
By centralizing user-level permissions, the system obtains user permission information under preset transaction verification items, performs comprehensive verification based on the verification pass conditions, and generates current transaction instruction information.
It improves the comprehensiveness and coverage of permission verification during user transactions, enhances the timeliness and effectiveness of transactions, and avoids security risks caused by missing permission verification.
Smart Images
Figure CN121745937A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of data processing technology, specifically to a transaction implementation method, apparatus, device, and storage medium. Background Technology
[0002] For various business applications developed in the Internet field, in order to ensure the security of user transactions within the business application, different functional permissions are usually set for each user for different business functions within the business application, so as to control the user's secure access and operation of various business functions within the business application.
[0003] However, as various business processes within the application develop further, user permissions configured in the above manner become increasingly fragmented. When users initiate corresponding transactions within the application, it becomes impossible to perform a comprehensive verification of user permissions in a timely and effective manner, thus failing to guarantee the security of user transactions. Summary of the Invention
[0004] This application provides a transaction implementation method, apparatus, device, and storage medium, which realizes permission aggregation and verification for each user transaction from the user's perspective, improves the comprehensiveness and coverage of permission verification for each user transaction, and ensures the security of user transactions.
[0005] In a first aspect, embodiments of this application provide a transaction implementation method, the method comprising: In response to a current transaction request initiated by any user, the user's permission aggregation information under the preset transaction verification items is obtained based on the user's user identifier; Based on the verification pass conditions of the current transaction request under the transaction verification item, the permission aggregation information is verified to obtain the verification result of the user under the transaction verification item. Based on the user's verification result under the transaction verification item, the user's current transaction instruction information is generated.
[0006] Secondly, embodiments of this application provide a transaction implementation apparatus, the apparatus comprising: The transaction permission acquisition module is used to respond to any user's current transaction request and obtain the user's permission aggregation information under preset transaction verification items based on the user's user identifier. The transaction permission verification module is used to verify the permission aggregation information according to the verification pass conditions of the current transaction request under the transaction verification item, and obtain the verification result of the user under the transaction verification item. The transaction implementation module is used to generate the user's current transaction instruction information based on the user's verification result under the transaction verification item.
[0007] Thirdly, embodiments of this application provide an electronic device, which includes: A processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the transaction implementation method provided in any embodiment of this application.
[0008] Fourthly, embodiments of this application provide a computer-readable storage medium for storing a computer program that causes a computer to execute the transaction implementation method provided in any embodiment of this application.
[0009] Fifthly, embodiments of this application provide a computer program product, including a computer program / instructions, which, when executed by a processor, implement the transaction implementation method provided in any embodiment of this application.
[0010] The technical solution provided in this application, upon detecting a current transaction request initiated by any user, first obtains the user's permission aggregation information under preset transaction verification items based on the user identifier. This achieves comprehensive permission acquisition for each user transaction through user-level permission aggregation configuration. Then, by analyzing the verification pass conditions of the current transaction request under the aforementioned transaction verification items, the user's permission aggregation information is comprehensively verified. Based on the verification results of the user under the transaction verification items, the user's current transaction instruction information is generated. This achieves permission aggregation verification for each user transaction from the user perspective, improving the comprehensiveness and coverage of permission verification for each transaction, enhancing the timeliness and effectiveness of permission verification for each transaction, avoiding the broken window effect in the transaction process due to missing verification of some permissions, and ensuring user transaction security. Attached Figure Description
[0011] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0012] Figure 1 A flowchart illustrating a transaction implementation method provided in this application embodiment; Figure 2 A flowchart illustrating another transaction implementation method provided in this application embodiment; Figure 3 A schematic block diagram of a transaction implementation device provided in an embodiment of this application; Figure 4A schematic block diagram of an electronic device provided in an embodiment of this application. Detailed Implementation
[0013] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.
[0014] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. 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 server that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.
[0015] In this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or solution described as "exemplary" or "for example" in this application should not be construed as being better or more advantageous than other embodiments or solutions. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.
[0016] In the description of the embodiments in this application, unless otherwise stated, "multiple" means two or more, that is, at least two. "At least one" means one or more. "Any" means any one or any several.
[0017] It should be noted that all information (including but not limited to the user's identity information, transaction information, various permission information, and other related personal information), data (including but not limited to data used for analysis, stored data, and displayed data), and signals involved in this application have been authorized by the user or fully authorized by all parties, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, the user's identity data, permission data, and specific transaction data involved in this application were all obtained with full authorization.
[0018] Because the functional permissions configured for each user under different business functions in business applications are relatively dispersed, it is impossible to perform a comprehensive and timely verification of user permissions for each transaction, thus compromising transaction security. To address this, this application proposes a novel transaction implementation scheme. By pre-setting multiple transaction verification items and verification pass conditions for each transaction scenario, it supports centralized permission configuration at the user level. Therefore, each time a user initiates a transaction, the user identifier can be used to comprehensively obtain the user's permission aggregation information under the preset transaction verification items. The verification pass conditions for each transaction scenario are then used to perform a comprehensive verification of this permission aggregation information, thereby generating the user's current transaction instruction information. This improves the comprehensiveness and coverage of permission verification for each transaction, ensuring user transaction security.
[0019] Figure 1 This is a flowchart illustrating a transaction implementation method provided in an embodiment of this application. This method can be executed by the transaction implementation device provided in this application. The transaction implementation device can be implemented using any software and / or hardware method. Exemplarily, the transaction implementation device can be applied to any electronic device, including but not limited to tablet computers, mobile phones (such as foldable phones, large-screen phones, etc.), wearable devices, in-vehicle devices, laptop computers, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), smart TVs, smart screens, high-definition TVs, 4K TVs, smart speakers, smart projectors, and other various computing devices. This disclosure does not impose any restrictions on the specific type of electronic device.
[0020] Specifically, such as Figure 1 As shown, the method may include the following steps: S110, in response to any current transaction request initiated by a user, obtains the user's permission aggregation information under the preset transaction verification items based on the user's user identifier.
[0021] Various financial trading platforms typically offer users a variety of financial products represented by different trading instruments, enabling users to invest in and trade these instruments using their resources, thereby maximizing the value and benefits of their resources. These trading instruments can be financial products such as stocks, funds, and options, or combinations of one or more of these products. Since different users may have different access permissions to different specific trading functions within a financial trading platform, to ensure transaction security, it is usually necessary to verify user permissions for each transaction before it is initiated, controlling secure access to these various trading functions within the financial trading platform.
[0022] In this application, considering that the functional permissions configured for each user under different transaction sub-functions are relatively dispersed, it is impossible to perform a timely and effective comprehensive verification of user permissions for each transaction. Therefore, to ensure user transaction security, it is first necessary to ensure a comprehensive verification of user permissions for each transaction.
[0023] Therefore, for various trading scenarios within a financial trading platform, this application can provide a capability for centralized configuration of user permissions, so that each subsequent transaction by a user can fully acquire and verify the user's relevant permissions from the user's perspective.
[0024] Specifically, this application can analyze, based on transaction risk control considerations, which types of information related to each user will affect the successful completion of transactions in various transaction scenarios. In this way, multiple transaction verification items are pre-set, so that each transaction verification item can represent a transaction influencing factor in determining whether a user's transaction can be successfully completed in various transaction scenarios. This allows users to use each transaction verification item to complete the centralized configuration of user permissions in various transaction scenarios.
[0025] For example, considering which business transaction functions a user account is restricted from, whether the user account is closed or becomes a read-only account, and which types of transaction targets the user account can support for normal transactions, all of these factors will affect the user's successful transactions in various transaction scenarios.
[0026] In one embodiment, the transaction verification items in this application may include at least the user's account business restriction verification items, account status verification items, and transaction category verification items.
[0027] The Account Business Restriction Verification item describes the specific business transaction functions that a user account may be restricted from using. For example, a user account may be restricted from opening fund positions or subscribing to stocks. Furthermore, the permission aggregation information under the Account Business Restriction Verification item includes all the restricted business transaction functions currently available to a user account.
[0028] The account status verification item describes the specific status of a user account, such as whether the account is normally activated, read-only, or closed. Furthermore, the permission aggregation information under the account status verification item includes the account status information of a specific user account.
[0029] The transaction category verification item describes the various types of trading instruments supported by a user account. For example, a user account may support trading in funds, stocks, and bonds. Furthermore, the permission aggregation information under the transaction category verification item includes all the transaction categories currently supported by a user account.
[0030] Therefore, to ensure user transaction security, each user, after logging into the financial trading platform, can use the user-level permission aggregation configuration component module provided by the platform to obtain the permission aggregation information of the user identifier carried in the current transaction request under preset transaction verification items. Thus, this application enables the aggregation configuration of user permissions at the user level within the financial trading platform, achieving comprehensive centralized management of user-level permissions.
[0031] In this application, to ensure user transaction security, it is typically used to monitor in real time whether a user executes a corresponding transaction trigger operation for any trading instrument within the financial trading platform, in order to determine whether the user has an actual trading need for any trading instrument. Therefore, upon detecting a user's execution of a transaction trigger operation for any trading instrument, a corresponding current transaction request can be generated and reported to the server so that the server can respond to the transaction promptly. The current transaction request may include the user identifier that initiated the transaction.
[0032] Therefore, upon receiving a current transaction request initiated by any user, this application first parses the current transaction request to determine the specific user identifier of the user initiating the transaction. Then, using this user identifier, it retrieves the user's permission configuration information for each transaction verification item, thus obtaining the user's permission aggregation information across all transaction verification items in this application.
[0033] S120: Based on the verification pass conditions of the current transaction request under the transaction verification item, verify the permission aggregation information to obtain the user's verification result under the transaction verification item.
[0034] Considering that successful transactions require different permission checks in different scenarios, this application provides both a centralized configuration capability for user permissions and a capability to customize permission check configurations based on specific conditions for each transaction scenario, in order to ensure user transaction security.
[0035] Specifically, this application can also support the ability to customize the permission verification pass conditions for each transaction scenario, so as to pre-configure the user's verification pass conditions for each transaction scenario.
[0036] Specifically, after detecting a verification condition configuration request initiated through the above-mentioned verification pass condition configuration capability, a corresponding transaction scenario input page will first be generated and displayed to business personnel to select and input verification pass conditions under different transaction scenarios, thereby achieving pre-configuration, such as pre-configuring verification pass conditions for the fund subscription transaction scenario.
[0037] After detecting that the business personnel have entered the confirmation operation for the verification pass conditions for different transaction scenarios, this application can obtain the preset transaction verification items to be verified under the corresponding transaction scenario based on the scenario description information for different transaction scenarios, and obtain the configuration information of the verification pass conditions under these transaction verification items, so as to realize the customized configuration of the verification pass conditions under each transaction verification item for each transaction scenario.
[0038] For example, in the transaction scenario of fund subscription, the verification condition configured under the account business restriction verification item can be that the user account does not have the ability to open a fund position or upgrade the account among all the restricted business transaction functions; under the account status verification item, the verification condition configured can be that the user account status is in a normal enabled state; under the transaction category verification item, the verification condition configured can be that the user account supports the fund type among the various transaction target types.
[0039] For example, in the transaction scenario of fund redemption, under the account business restriction verification item, the configured verification pass condition can be that the user account's current restricted business transaction functions do not include fund opening capability and account upgrade; under the account status verification item, the configured verification pass condition can be that the user account status is in normal enabled state; the transaction category verification item is not a preset transaction verification item in this transaction scenario, that is, it does not involve the verification of the transaction category verification item.
[0040] In this application, to ensure transaction security for users in each transaction scenario, when a transaction trigger operation is detected that a user has performed on any transaction target, this application can analyze not only the user identifier that initiated the transaction, but also the specific target type and transaction operation type that the user is targeting in this transaction, in order to generate a corresponding current transaction request. This allows the current transaction request to carry not only the user identifier that initiated the transaction, but also the target type and transaction operation type of the user's current transaction, so as to accurately analyze the current transaction scenario in which the user is in each transaction.
[0041] Therefore, upon receiving a current transaction request initiated by any user, this application parses the current transaction request to determine not only the user identifier who initiated the transaction, but also the type of transaction target and the type of transaction operation targeted by the user. Then, based on the type of transaction target and the type of transaction operation targeted by the user, it analyzes which specific transaction the user is executing for which transaction target, thereby determining the current transaction scenario in which the user is currently conducting the transaction.
[0042] Furthermore, by utilizing the user identifier and the scenario description information of the current transaction scenario, the pre-configured verification conditions for each transaction verification item under various pre-configured verification conditions in different transaction scenarios can be identified and used as the verification conditions in this application. Then, using the verification conditions under each transaction verification item, the user's permission aggregation information under each transaction verification item can be verified one-to-one to determine whether the user's permission aggregation information under each transaction verification item passes the verification, thereby obtaining the verification result for the user under each transaction verification item and ensuring the accuracy of permission verification for each user transaction.
[0043] S130: Generate the user's current transaction instruction information based on the user's verification result under the transaction verification item.
[0044] By comprehensively analyzing the verification results of each transaction verification item, it is determined whether the user supports a successful transaction in the current transaction scenario, thereby generating the user's current transaction instruction information, which may include both current transaction execution information and current transaction rejection information.
[0045] In some embodiments, the current transaction instruction information of a user can be generated in the following manner: if the user passes the verification under each transaction verification item, the current transaction execution information of the user is generated; if the user fails the verification under at least one transaction verification item, the current transaction rejection information of the user is generated.
[0046] In other words, by comprehensively analyzing the verification results of each transaction verification item, it is determined whether the user has passed the verification for each item. If the user passes all verification items, it indicates that the user has the authority to successfully complete the transaction in the current transaction scenario. This generates the user's current transaction execution information, and based on this information, a timely and effective transaction response is provided to any new transaction requests initiated by the user. Conversely, if the user fails at least one verification item, it indicates that the user does not have the authority to successfully complete the transaction in the current transaction scenario. This generates a current transaction rejection message, which is then fed back to the user. This rejection message may include the reason for the rejection.
[0047] The technical solution provided in this application, upon detecting a current transaction request initiated by any user, first obtains the user's permission aggregation information under preset transaction verification items based on the user identifier. This achieves comprehensive permission acquisition for each user transaction through user-level permission aggregation configuration. Then, by analyzing the verification pass conditions of the current transaction request under the aforementioned transaction verification items, the user's permission aggregation information is comprehensively verified. Based on the verification results of the user under the transaction verification items, the user's current transaction instruction information is generated. This achieves permission aggregation verification for each user transaction from the user perspective, improving the comprehensiveness and coverage of permission verification for each transaction, enhancing the timeliness and effectiveness of permission verification for each transaction, avoiding the broken window effect in the transaction process due to missing verification of some permissions, and ensuring user transaction security.
[0048] As an optional implementation in this application, to ensure the efficiency and convenience of configuring user permissions from the user perspective, this application can pre-design a transaction component for various transaction scenarios within a financial trading platform. This transaction component can support timely and effective transaction responses to each transaction request initiated by any user. Furthermore, this transaction component can be used to obtain permission aggregation information for any user under all preset transaction verification items, thus enabling the centralized configuration of user permissions. Additionally, this transaction component can also be used for customized configuration of verification pass conditions for each transaction scenario.
[0049] Therefore, in order to ensure that users fully acquire and accurately verify permissions for each transaction, this application can provide a detailed explanation of the entire transaction process for each user transaction.
[0050] Figure 2 A flowchart of another transaction implementation method provided in this application embodiment, the method specifically may include the following steps: S210, in response to any current transaction request initiated by a user, determines the transaction verification items provided by the preset transaction component.
[0051] For the preset trading components within the financial trading platform, users can trigger these components to complete the centralized configuration of user permissions under each trading verification item and the customized configuration of verification pass conditions for each trading scenario under each trading verification item.
[0052] Therefore, upon receiving a current transaction request initiated by any user, this application will first call the preset transaction component to parse the current transaction request, in order to determine the user identifier of the user initiating the transaction and the various transaction verification items provided by the preset transaction component, so as to enable the user to fully acquire permissions under each transaction verification item.
[0053] S220 uses a preset transaction component to read the user's user identifier and outputs the permission aggregation information configured for the user under each transaction verification item.
[0054] It is understood that the preset transaction component in this application can enable users to complete the centralized configuration of user permissions under each transaction verification item by triggering the preset transaction component.
[0055] Therefore, after determining the user identifier that initiated the transaction, this application can read the user identifier through a preset transaction component to quickly and effectively find the specific permission information that the user has pre-configured under each transaction verification item by triggering the preset transaction component. This information is then output as the permission aggregation information that the user has configured under each transaction verification item, thereby comprehensively and accurately obtaining the permission aggregation information of the user under each transaction verification item from the user's perspective, and improving the comprehensiveness and coverage of permission verification for each transaction.
[0056] S230, Based on the transaction type and transaction object corresponding to the current transaction request, determine the corresponding adaptation permission verifier, which includes the verification pass conditions under the transaction verification item.
[0057] It should be understood that after parsing the current transaction request through the preset transaction components, this application will also determine the specific target type and transaction operation type of the user's current transaction, thereby obtaining the transaction type and transaction object corresponding to the current transaction request. The transaction type can indicate which of various transaction operations, such as subscription or redemption, the user's current transaction can be, while the transaction object can indicate the specific target of the user's current transaction.
[0058] To ensure accurate verification of user permissions for each transaction, this application can generate a permission verifier for each transaction scenario based on the customized verification pass conditions configured for each transaction verification item. The permission verifier for each transaction scenario can accurately describe the verification pass conditions configured for each transaction verification item for that transaction scenario.
[0059] After determining the transaction type and transaction object corresponding to the current transaction request, this application determines the current transaction scenario based on the specific transaction operation represented by the transaction type and the specific transaction target represented by the transaction object. Then, by using a preset transaction component based on the scenario description information of the current transaction scenario, the corresponding permission verifier can be determined, which serves as the adaptive permission verifier in this application.
[0060] S240, based on the verification pass conditions under the transaction verification item, verify the permission aggregation information to obtain the user's verification result under the transaction verification item.
[0061] After determining the appropriate permission validator for the current transaction scenario, this application can utilize the configured verification pass conditions under each transaction verification item in the appropriate permission validator to perform one-to-one verification of the user's permission collection information under each transaction verification item, so as to determine whether the user's permission collection information under each transaction verification item passes the verification, thereby obtaining the user's verification result under each transaction verification item, and ensuring the accuracy of permission verification for each user transaction.
[0062] Furthermore, in one embodiment, a user identifier can be input into a transaction component. The transaction component obtains the permission aggregation information of the user corresponding to the user identifier under all transaction verification items. Based on the user identifier and the corresponding permission aggregation information, data to be verified is generated. Subsequently, the data to be verified can be input into an adaptive permission verifier. The data to be verified includes an encrypted identifier array corresponding to the user identifier and an encrypted permission array corresponding to the permission aggregation information. Specifically, after obtaining the permission aggregation information of the user corresponding to the user identifier under all transaction verification items, a first pseudo-random number generator corresponding to the identifier type can be determined based on the identifier type of the user identifier. An encrypted random number is generated based on the user identifier using the first pseudo-random number, and then the user identifier is encrypted using the encrypted random number to obtain the encrypted identifier array corresponding to the user identifier. Simultaneously, the permission aggregation information is encrypted using the encrypted random number to obtain the encrypted permission data corresponding to the permission aggregation information. It is understood that the above encryption process may include one-round encryption algorithms or multiple-round encryption algorithms. Encryption algorithms include, but are not limited to, hash encryption, MD5 encryption algorithms, etc., which are not limited here.
[0063] After obtaining the data to be verified, the adaptive permission verifier can determine the pseudo-random number generator corresponding to the identifier type corresponding to the real user identifier based on the user identifier in the current transaction request (here, we can call it the real user identifier). This allows it to obtain a second pseudo-random number generator for the identifier type corresponding to the real user identifier. Based on the real user identifier, a decryption random number is generated using this second pseudo-random number. This decryption random number is then used to decrypt the encrypted identifier array in the data to be verified, obtaining the user identifier carried in the data. Simultaneously, the same decryption random number is used to decrypt the encrypted permission array in the data to obtain the permission aggregation information carried in the data. Subsequently, the verification pass conditions configured under each transaction verification item in the adaptive permission verifier can be used to perform a one-to-one verification of the decrypted permission aggregation information carried in the data to be verified, to determine whether the user's permission aggregation information under each transaction verification item passes the verification.
[0064] Understandably, if the user identifier used by the adaptation permission verifier (i.e., the real user identifier) is consistent with the user identifier used by the transaction component, the user identifier obtained by decrypting the encrypted identifier array in the data to be verified using the decryption random number will be consistent with the user identifier in the current transaction request. In this case, the permission aggregation information obtained by decrypting the encrypted permission array in the data to be verified using the decryption random number (i.e., the permission aggregation information carried by the aforementioned data to be verified) will also be the permission aggregation information of the user identifier in the current transaction request. If the user identifier used by the adaptation permission verifier (i.e., the real user identifier) is inconsistent with the user identifier used by the transaction component, the user identifier obtained by decrypting the encrypted identifier array in the data to be verified using the decryption random number will be inconsistent with the user identifier in the current transaction request. In this case, the permission aggregation information obtained by decrypting the encrypted permission array in the data to be verified using the decryption random number (i.e., the permission aggregation information carried by the aforementioned data to be verified) will also not be the permission aggregation information of the user identifier in the current transaction request.
[0065] When the transaction component sends permission aggregation information to the adaptive permission verifier, encrypting the user identifier and permission aggregation information ensures the confidentiality of user-related information, prevents data from being cracked during transmission, and improves data security. At the same time, during the data decryption process of the adaptive permission verifier, a second verification of the user identifier and permission aggregation information can be performed, ensuring the correlation between the obtained permission aggregation information and the user who initiated the current transaction request, and improving the accuracy of permission verification.
[0066] In some embodiments, considering that certain transaction segmentation functions may only focus on specific transaction verification items, while ignoring others, this application, in order to ensure efficient and accurate permission verification for each user transaction, not only customizes the verification pass conditions for each transaction verification item for each transaction scenario using preset transaction components, but also configures corresponding flag information for each transaction verification item based on the specific focus of each transaction scenario on each verification item. For example, assuming that for any transaction scenario's verification pass condition configuration, a flag of a certain transaction verification item is "1", it indicates that the transaction scenario focuses on this transaction verification item. Conversely, a flag of a certain transaction verification item is "0", indicating that the transaction scenario does not focus on this transaction verification item.
[0067] Therefore, this application can accomplish the permission aggregation verification of users under each transaction verification item in the following way: determine the first type of verification item and the second type of verification item based on the flag information of each transaction verification item; verify the permission aggregation information under the first type of verification item according to the verification pass conditions under the first type of verification item, and generate the actual verification result under the first type of verification item; generate the user's verification result under the transaction verification item based on the actual verification result under the first type of verification item and the exemption verification result under the second type of verification item.
[0068] The first type of verification item can be the transaction verification item that is of primary concern in the current transaction scenario, while the second type of verification item can be the transaction verification item that is not of primary concern in the current transaction scenario.
[0069] Specifically, after determining the appropriate permission verifier for the current transaction scenario, this application can first determine the flag information of each transaction verification item in the appropriate permission verifier, so as to accurately classify each transaction verification item and obtain the first type of verification item and the second type of verification item.
[0070] Then, based on the first type of verification item as the key transaction verification item in the current transaction scenario, this application can use the verification pass conditions under each first type of verification item to perform one-to-one verification of the user's permission collection information under each first type of verification item, to determine whether the user's permission collection information under each first type of verification item passes the verification, thereby obtaining the user's real verification result under each first type of verification item.
[0071] Moreover, since the second type of verification item is a transaction verification item that is not of concern in the current transaction scenario, this application does not need to actually verify the user permissions under the second type of verification item, but can directly exempt the permission verification under each second type of verification item, thereby obtaining the user's exemption verification result under each second type of verification item, which indicates that the user's permission aggregation information under each second type of verification item has passed the verification.
[0072] Therefore, by merging the user's actual verification results for each first-category verification item and the user's exempted verification results for each second-category verification item, the user's verification result for each transaction verification item can be obtained.
[0073] S250 generates the user's current transaction instruction information based on the user's verification result under the transaction verification item.
[0074] The technical solution provided in this application, upon detecting a current transaction request initiated by any user, first uses a preset transaction component to read the user identifier to obtain the user's permission aggregation information under each transaction verification item. This allows for comprehensive permission acquisition for each user transaction through user-level permission aggregation configuration. Then, by analyzing the verification pass conditions of the current transaction request under the aforementioned transaction verification items, the user's permission aggregation information is comprehensively verified. Based on the verification results of the user under the transaction verification items, the user's current transaction instruction information is generated. This achieves permission aggregation verification for each user transaction from the user's perspective, improving the comprehensiveness and coverage of permission verification for each transaction, enhancing the timeliness and effectiveness of permission verification for each transaction, avoiding the broken window effect in the transaction process due to missing verification of some permissions, and ensuring the security of user transactions.
[0075] Figure 3 This is a schematic block diagram of a transaction implementation device provided in an embodiment of this application. Figure 3 As shown, the device 300 may include: The transaction permission acquisition module 310 is used to respond to a current transaction request initiated by any user and obtain the permission aggregation information of the user under the preset transaction verification items based on the user's user identifier. The transaction permission verification module 320 is used to verify the permission aggregation information according to the verification pass conditions of the current transaction request under the transaction verification item, and obtain the verification result of the user under the transaction verification item. The transaction implementation module 330 is used to generate the user's current transaction instruction information based on the user's verification result under the transaction verification item.
[0076] In some possible implementations, the transaction permission acquisition module 310 can be specifically used for: In response to any current transaction request initiated by a user, determine the transaction verification items provided by the preset transaction components; The user identifier of the user is read using the preset transaction component, so as to output the permission aggregation information configured for the user under each transaction verification item.
[0077] In some implementations, the transaction permission verification module 320 can be specifically used for: Based on the transaction type and transaction object corresponding to the current transaction request, a corresponding adaptive permission verifier is determined. The adaptive permission verifier includes the verification pass conditions under the transaction verification item. Based on the verification pass conditions under the transaction verification item, the permission aggregation information is verified to obtain the user's verification result under the transaction verification item.
[0078] In some implementations, the transaction permission verification module 320 can also be specifically used for: Based on the flag information of each transaction verification item, determine the first type of verification item and the second type of verification item; Based on the verification pass conditions under the first type of verification item, the permission aggregation information under the first type of verification item is verified to generate the actual verification result under the first type of verification item. Based on the actual verification results under the first type of verification item and the exemption verification results under the second type of verification item, the verification result of the user under the transaction verification item is generated.
[0079] In some possible implementations, the transaction implementation module 330 can be specifically used for: If the user passes the verification for each transaction verification item, then the user's current transaction execution information is generated; If the user fails verification in at least one transaction verification item, a current transaction rejection message for the user is generated.
[0080] In some implementations, the transaction verification items include at least the user's account business restriction verification items, account status verification items, and transaction category verification items.
[0081] In this embodiment, upon detecting a current transaction request initiated by any user, the system first obtains the user's permission aggregation information under preset transaction verification items based on the user identifier. This allows for comprehensive permission acquisition for each user transaction through user-level permission aggregation configuration. Then, by analyzing the verification pass conditions of the current transaction request under the aforementioned transaction verification items, the user's permission aggregation information is comprehensively verified. Based on the verification results under the transaction verification items, the system generates the user's current transaction instruction information. This achieves permission aggregation verification for each user transaction from the user perspective, improving the comprehensiveness and coverage of permission verification for each transaction, enhancing the timeliness and effectiveness of permission verification, preventing the broken window effect in the transaction process due to missing verification of some permissions, and ensuring user transaction security.
[0082] It should be understood that the above-described apparatus embodiments and the method embodiments provided in this application can correspond to each other, and similar descriptions can be referred to the method embodiments. To avoid repetition, further details are omitted here. Specifically, Figure 3 The apparatus 300 shown can execute any of the method embodiments provided in this application, and the foregoing and other operations and / or functions of each module in the apparatus 300 are respectively for implementing the corresponding processes in the various methods provided in the embodiments of this application. For the sake of brevity, they will not be described in detail here.
[0083] The apparatus 300 of this application embodiment has been described above from the perspective of functional modules in conjunction with the accompanying drawings. It should be understood that this functional module can be implemented in hardware, in software instructions, or in a combination of hardware and software modules. Specifically, the steps of the method embodiments applied to the server in this application embodiment can be completed by integrated logic circuits in the processor hardware and / or by software instructions. The steps of the method applied in this application embodiment can be directly manifested as execution by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. Optionally, the software module can be located in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps in the above method embodiments.
[0084] Figure 4 A schematic block diagram of an electronic device provided in an embodiment of this application.
[0085] like Figure 4 As shown, the electronic device 400 may include: The system includes a memory 410 and a processor 420. The memory 410 stores computer programs and transfers the program code to the processor 420. In other words, the processor 420 can retrieve and run the computer program from the memory 410 to implement the methods described in the embodiments of this application.
[0086] For example, the processor 420 can be used to execute the above-described method embodiments according to instructions in the computer program.
[0087] In some embodiments of this application, the processor 420 may include, but is not limited to: General-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
[0088] In some embodiments of this application, the memory 410 includes, but is not limited to: Volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).
[0089] In some embodiments of this application, the computer program may be divided into one or more modules, which are stored in the memory 410 and executed by the processor 420 to perform the method provided in this application. The one or more modules may be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of the computer program in the electronic device.
[0090] like Figure 4 As shown, the electronic device may also include: Transceiver 430, which can be connected to processor 420 or memory 410.
[0091] The processor 420 can control the transceiver 430 to communicate with other devices; specifically, it can send information or data to other devices or receive information or data sent by other devices. The transceiver 430 may include a transmitter and a receiver. The transceiver 430 may further include antennas, and the number of antennas may be one or more.
[0092] It should be understood that the various components in the electronic device are connected through a bus system, which includes a data bus, a power bus, a control bus, and a status signal bus.
[0093] This application also provides a computer storage medium storing a computer program thereon, which, when executed by a computer, enables the computer to perform the methods of the above-described method embodiments. Alternatively, this application also provides a computer program product containing instructions that, when executed by a computer, cause the computer to perform the methods of the above-described method embodiments.
[0094] When implemented using software, it can be implemented entirely or partially as 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 medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital video disc (DVD)), or a semiconductor medium (e.g., solid-state disk (SSD)).
[0095] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments claimed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0096] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.
[0097] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. For example, the functional modules in the various embodiments of this application may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.
[0098] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A method for implementing a transaction, characterized in that, include: In response to a current transaction request initiated by any user, the user's permission aggregation information under the preset transaction verification items is obtained based on the user's user identifier; Based on the verification pass conditions of the current transaction request under the transaction verification item, the permission aggregation information is verified to obtain the verification result of the user under the transaction verification item. Based on the user's verification result under the transaction verification item, the user's current transaction instruction information is generated.
2. The method according to claim 1, characterized in that, The response to a current transaction request initiated by any user includes obtaining the user's permission aggregation information under preset transaction verification items based on the user's user identifier, including: In response to any current transaction request initiated by a user, determine the transaction verification items provided by the preset transaction components; The user identifier of the user is read using the preset transaction component, so as to output the permission aggregation information configured for the user under each transaction verification item.
3. The method according to claim 1, characterized in that, The step of verifying the permission aggregation information based on the verification pass conditions of the current transaction request under the transaction verification item, and obtaining the user's verification result under the transaction verification item, includes: Based on the transaction type and transaction object corresponding to the current transaction request, a corresponding adaptive permission verifier is determined. The adaptive permission verifier includes the verification pass conditions under the transaction verification item. Based on the verification pass conditions under the transaction verification item, the permission aggregation information is verified to obtain the user's verification result under the transaction verification item.
4. The method according to claim 3, characterized in that, The step of verifying the permission aggregation information according to the verification pass conditions under the transaction verification item to obtain the user's verification result under the transaction verification item includes: Based on the flag information of each transaction verification item, determine the first type of verification item and the second type of verification item; Based on the verification pass conditions under the first type of verification item, the permission aggregation information under the first type of verification item is verified to generate the actual verification result under the first type of verification item. Based on the actual verification results under the first type of verification item and the exemption verification results under the second type of verification item, the verification result of the user under the transaction verification item is generated.
5. The method according to claim 1, characterized in that, The step of generating the user's current transaction instruction information based on the user's verification result under the transaction verification item includes: If the user passes the verification for each transaction verification item, then the user's current transaction execution information is generated; If the user fails verification in at least one transaction verification item, a current transaction rejection message for the user is generated.
6. The method according to claim 1, characterized in that, The transaction verification items include at least the user's account business restriction verification items, account status verification items, and transaction category verification items.
7. A transaction realization apparatus, characterized in that, include: The transaction permission acquisition module is used to respond to any user's current transaction request and obtain the user's permission aggregation information under preset transaction verification items based on the user's user identifier. The transaction permission verification module is used to verify the permission aggregation information according to the verification pass conditions of the current transaction request under the transaction verification item, and obtain the verification result of the user under the transaction verification item. The transaction implementation module is used to generate the user's current transaction instruction information based on the user's verification result under the transaction verification item.
8. An electronic device, characterized in that, include: A processor and a memory, the memory being used to store a computer program, the processor being used to invoke and run the computer program stored in the memory to perform the transaction implementation method according to any one of claims 1-6.
9. A computer-readable storage medium, characterized in that, Used to store a computer program that causes a computer to perform the transaction implementation method as described in any one of claims 1-6.
10. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the transaction implementation method as described in any one of claims 1-6.