Transaction processing method and device, storage medium and electronic equipment

Abstract

The invention provides a transaction processing method and device, a storage medium and electronic device.The method is applied to a server side and comprises the steps that template generation data corresponding to a preset transaction type is obtained, a transaction identifier and static data of the preset transaction type in the template generation data are obtained, and the transaction identifier and the static data are stored in the server side; a dynamic field and a field identifier in the template generation data are acquired, a target field parameter corresponding to the dynamic field is configured, the target field parameter comprises a data acquisition rule and a data protection rule, and a target transaction data template corresponding to a preset transaction type is generated based on the static data and the dynamic field, the target transaction data template is used for generating target transaction data corresponding to the preset transaction type, storing the target transaction data template based on the transaction identifier, and storing the dynamic field based on the field identifier. By adopting the method, the convenience of generating the transaction template by the user is improved, and the transaction data is generated according to the target transaction data template, so that the efficiency of transaction processing is improved.

Description

Technical Field

[0001] This specification relates to the field of computer technology, and more specifically, to a transaction processing method, device, storage medium, and electronic device in the field of computer technology. Background Art

[0002] Nowadays, with the continuous development of the economy, contracts need to be signed when handling various affairs. In order to improve the efficiency of handling affairs, electronic contracts are provided to complete the handling of affairs. However, in the process of generating electronic contracts, since the contract needs to be rendered on the application side, the data processing capacity of the application side is insufficient, resulting in contract generation being stuck or even failing, affecting the user's handling of affairs. Summary of the Invention

[0003] This specification provides a transaction processing method, device, storage medium and electronic device. The method can customize the parameters of dynamic fields in the transaction template according to needs, and by pre-storing the generated target transaction data template, it is convenient to subsequently generate corresponding target transaction data for the preset transaction type, thereby improving the convenience of users generating transaction templates, and generating transaction data according to the target transaction data template, thereby improving the efficiency of transaction processing.

[0004] In a first aspect, a transaction processing method is provided, the method comprising:

[0005] Acquire template generation data corresponding to a preset transaction type, and acquire a transaction identifier and static data of the preset transaction type in the template generation data;

[0006] Acquire dynamic fields and field identifiers in the template-generated data, and configure target field parameters corresponding to the dynamic fields, wherein the target field parameters include data acquisition rules and data protection rules;

[0007] generating a target transaction data template corresponding to the preset transaction type based on the static data and the dynamic field, wherein the target transaction data template is used to generate target transaction data corresponding to the preset transaction type;

[0008] The target transaction data template is stored based on the transaction identifier, and the dynamic field is stored based on the field identifier.

[0009] Through the above technical solution, data can be generated according to the acquired template, transaction identification and static data, as well as dynamic fields and field identification can be obtained. After the parameters of the dynamic fields are configured, a target transaction template corresponding to the transaction identification is generated, so that the parameters of the dynamic fields in the transaction template can be customized according to needs, and by pre-storing the generated target transaction data template, it is convenient to subsequently generate corresponding target transaction data for the preset transaction type, thereby improving the convenience of users generating transaction templates, and generating transaction data according to the target transaction data template, thereby improving the efficiency of transaction processing.

[0010] In conjunction with the first aspect, in some possible implementations, obtaining the dynamic field and field identifier in the template-generated data and configuring the target field parameters corresponding to the dynamic field include:

[0011] Obtaining the dynamic fields in the template-generated data, as well as the field identifiers and field types corresponding to the dynamic fields;

[0012] Determine a data source corresponding to the field type, and configure a data acquisition rule corresponding to the field identifier based on the data source, wherein the data acquisition rule indicates a method for acquiring dynamic data corresponding to the field identifier from the data source;

[0013] Determining a sensitivity level corresponding to the field type based on the field type and the preset transaction type;

[0014] If the sensitivity level indicates that the field type is a sensitive field, configuring a desensitization rule corresponding to the dynamic field based on the field type;

[0015] Based on the field type and the preset transaction type, a first encryption rule corresponding to the field identifier is configured, where the first encryption rule is used to encrypt dynamic data corresponding to the dynamic field, and the encrypted dynamic data is in a locked state.

[0016] Through the above technical solution, data is generated according to the received template, the field parameters of the dynamic field are configured, and by configuring data acquisition rules and data protection rules including desensitization rules and first encryption rules, customized settings of the properties of the dynamic field are achieved, thereby improving the convenience of users generating transaction templates.

[0017] In combination with the first aspect and the above implementation manner, in some possible implementation manners, generating the target transaction data template corresponding to the preset transaction type includes:

[0018] A second encryption rule corresponding to the target transaction data template is configured based on the preset transaction type, where the second encryption rule is used to encrypt the target transaction data corresponding to the target transaction data template.

[0019] Through the above technical solution, a second encryption rule is configured for the target transaction data, thereby providing another way to encrypt and protect the data, making it easier for users to set it according to their needs and improving the user experience.

[0020] In combination with the first aspect and the above implementation manner, in some possible implementation manners, storing the target transaction data template based on the transaction identifier and storing the dynamic field based on the field identifier includes:

[0021] Storing the target transaction data template in a first database based on the transaction identifier;

[0022] Based on the field identifier and the transaction identifier, the target field parameter of the dynamic field is stored in the second database and the local cache space of the server. The data reading priority of the local cache space is higher than that of the second database.

[0023] Through the above technical solution, the target transaction data template and target field parameters are stored in the cache space according to the transaction identifier and field identifier, thereby improving the reading convenience and accuracy of the target transaction data template and target field parameters, and further improving the reliability of generating target transaction data according to the target transaction data template and target field parameters.

[0024] In combination with the first aspect and the above implementation manner, in some possible implementation manners, storing the target transaction data template in the first database based on the transaction identifier includes:

[0025] Based on the transaction identifier, the target transaction data template is stored in the first database of the server and in the cluster cache space corresponding to the server cluster to which the server belongs. The data reading priority of the cluster cache space is higher than that of the first database.

[0026] In combination with the first aspect and the above implementation, in some possible implementations, storing the target transaction data template in the first database of the server and in the cluster cache space corresponding to the server cluster to which the server belongs based on the transaction identifier includes:

[0027] Acquire a transaction signing mode corresponding to the transaction identifier in the template generation data, wherein the transaction signing mode indicates a display mode of target transaction data corresponding to the target transaction data template;

[0028] Based on the transaction identifier, the transaction signing method and the target transaction data template are stored in the first database of the server and in the cluster cache space corresponding to the server cluster to which the server belongs.

[0029] In combination with the first aspect and the above implementation manner, in some possible implementation manners, if a historical transaction data template corresponding to the transaction identifier is stored in the cluster cache space corresponding to the server or the first database, the target transaction data template is updated to the historical transaction data template;

[0030] If the local cache space or the second database stores historical field parameters corresponding to the field identifier, the historical field parameters are updated with the target field parameters.

[0031] In a second aspect, a transaction processing method is provided, which is applied to a server and includes:

[0032] If the server receives the transaction data generation request transmitted by the application, determining the transaction type in the transaction data generation request;

[0033] If the transaction type is a preset transaction type, obtaining a target transaction data template corresponding to the preset transaction type, and obtaining a target field parameter corresponding to a dynamic field in the target transaction data template;

[0034] Acquire dynamic data corresponding to the dynamic field based on the data acquisition rule and data protection rule corresponding to the target field parameter;

[0035] generating target transaction data corresponding to the transaction data generation request based on the dynamic data and the static data in the target transaction data template;

[0036] The target transaction data is transmitted to the application end so as to be displayed on the application end.

[0037] Through the above technical solution, the target transaction data template is obtained according to the transaction identifier, and the target field parameters are obtained according to the field identifier of the dynamic field of the target transaction data template. The target field parameters are used to obtain the dynamic data corresponding to the dynamic field, and the target transaction data is generated according to the static data in the target transaction data template. The rendered target transaction data is transmitted to the application end for display, so that the target transaction data is generated according to the computing resources of the server end through the target transaction data template. This can not only avoid transaction processing failure caused by insufficient computing power on the application end, but also avoid data leakage during data transmission, thereby improving the efficiency, reliability and security of target transaction data generation.

[0038] In combination with the second aspect and the above implementation, in some possible implementations, obtaining the target transaction data template corresponding to the preset transaction type, parsing and obtaining the target field parameters corresponding to the dynamic fields in the target transaction actual template, includes:

[0039] Obtaining a transaction identifier of the preset transaction type, and obtaining a target transaction data template from a cluster cache space or a first database corresponding to the server based on the transaction identifier;

[0040] Parsing the target transaction data template to obtain static data and dynamic fields in the target transaction data template;

[0041] Based on the field identifier of the dynamic field, a target field parameter corresponding to the field identifier is acquired in the local cache space of the server or the second database.

[0042] In combination with the second aspect and the above implementations, in some possible implementations, acquiring the dynamic data corresponding to the dynamic field based on the data acquisition rules and data protection rules in the target field parameters includes:

[0043] Determining a data acquisition interface corresponding to the dynamic field in the server based on a data acquisition rule corresponding to the target field parameter;

[0044] Searching in the data source corresponding to the data acquisition interface to obtain the dynamic data corresponding to the dynamic field;

[0045] If the dynamic field is a sensitive field, the dynamic data is desensitized based on the desensitization rules in the data protection rules to obtain the desensitized dynamic data, and the desensitized dynamic data is determined as the dynamic data corresponding to the dynamic field.

[0046] In combination with the second aspect and the above implementation, in some possible implementations, transmitting the target transaction data to the application end so as to display the target transaction data on the application end includes:

[0047] Acquire, based on the preset transaction type, a transaction signing method corresponding to the target transaction data and a target encryption method corresponding to the preset transaction type;

[0048] encrypting the target transaction data and / or the dynamic data in the target transaction data based on the target encryption method to obtain encrypted target transaction data, wherein the dynamic data in the encrypted target transaction data is in a locked state;

[0049] The encrypted target transaction data and the transaction signing method are transmitted to the application end, so that the application end displays the encrypted target transaction data based on the transaction signing method.

[0050] In combination with the second aspect and the above implementation manner, in some possible implementation manners, encrypting the target transaction data and / or the dynamic data in the target transaction data based on the target encryption method includes:

[0051] encrypting the dynamic data in the target transaction data based on a first encryption rule corresponding to a field identifier of the dynamic data; and / or

[0052] The target transaction data is encrypted based on a second encryption rule corresponding to the preset transaction type.

[0053] In a third aspect, a transaction processing device is provided, the device comprising:

[0054] a data acquisition unit, configured to acquire template generation data corresponding to a preset transaction type, and acquire a transaction identifier and static data of the preset transaction type in the template generation data;

[0055] a configuration unit, configured to obtain dynamic fields and field identifiers in the template-generated data, and configure target field parameters corresponding to the dynamic fields, wherein the target field parameters include data acquisition rules and data protection rules;

[0056] a template generating unit, configured to generate a target transaction data template corresponding to the preset transaction type based on the static data and the dynamic field, wherein the target transaction data template is used to generate target transaction data corresponding to the preset transaction type;

[0057] A storage unit is configured to store the target transaction data template based on the transaction identifier and to store the dynamic field based on the field identifier.

[0058] In a fourth aspect, a transaction processing device is provided, the device comprising:

[0059] a type determining unit, configured to determine a transaction type in a transaction data generation request if the server receives the transaction data generation request transmitted by the application;

[0060] a template acquiring unit, configured to, if the transaction type is a preset transaction type, acquire a target transaction data template corresponding to the preset transaction type, and acquire a target field parameter corresponding to a dynamic field in the target transaction data template;

[0061] a data acquisition unit, configured to acquire dynamic data corresponding to the dynamic field based on a data acquisition rule and a data protection rule corresponding to the target field parameter;

[0062] a data generating unit, configured to generate target transaction data corresponding to the transaction data generation request based on the dynamic data and static data in the target transaction data template;

[0063] A data transmission unit is used to transmit the target transaction data to the application end so as to display the target transaction data on the application end.

[0064] In a fifth aspect, a computer program product is provided, which includes: computer program code, which, when running on a computer, enables the computer to execute the method in the above-mentioned first aspect or any possible implementation of the first aspect.

[0065] In a sixth aspect, a computer-readable storage medium is provided, which stores a computer program code. When the computer program code runs on a computer, the computer executes the method in the above-mentioned first aspect or any possible implementation of the first aspect.

[0066] In a seventh aspect, an electronic device is provided, comprising: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the steps of the above method. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] Figure 1 This is a system architecture diagram of a transaction processing method provided by an embodiment of this specification;

[0068] Figure 2 This is a flowchart of a transaction processing method provided by an embodiment of this specification;

[0069] Figure 3 This is a flowchart of a transaction processing method provided by an embodiment of this specification;

[0070] Figure 4 This is an example diagram of a data desensitization method provided in the embodiments of this specification;

[0071] Figure 5 This is an example diagram of a data desensitization method provided in the embodiments of this specification;

[0072] Figure 6 This is a flowchart of a transaction processing method provided by an embodiment of this specification;

[0073] Figure 7 This is a flowchart of a transaction processing method provided by an embodiment of this specification;

[0074] Figure 8 This is an example schematic diagram of generating target transaction data provided by an embodiment of this specification;

[0075] Figure 9 This is an example schematic diagram of encrypting target transaction data provided by an embodiment of this specification;

[0076] Figure 10 This is a schematic diagram of the structure of a transaction processing device provided in an embodiment of this specification;

[0077] Figure 11 This is a schematic diagram of the structure of a transaction processing device provided in an embodiment of this specification;

[0078] Figure 12 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this specification;

[0079] Figure 13 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this specification. DETAILED DESCRIPTION

[0080] The following will clearly and thoroughly describe the technical solutions in this specification with reference to the accompanying drawings. In the description of the embodiments of this specification, unless otherwise specified, " / " means or. For example, A / B can mean A or B. "And / or" in the text is only a description of the association relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of this specification, "multiple" means two or more than two.

[0081] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood to imply or suggest relative importance or implicitly indicate the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features.

[0082] Figure 1 This is a system architecture diagram of a transaction processing method provided by the embodiment of this specification. Figure 1As shown, the transaction processing method provided in the embodiment of this specification can be applied to a terminal device to implement the process of generating a target transaction data template. The system structure provided in the embodiment of this specification mainly includes a server 10, a user 20, a database 30 and an application 40. Among them, the server 10 can be a device with a data processing function, such as a personal computer, a smart phone, a tablet computer and the like, or an independent server or a server cluster composed of multiple servers, specifically but not limited to a hardware server, a virtual server, a cloud server and the like. The database 30 can be a device with a data storage function, such as a server, a personal computer and the like. The application 40 can be a device for requesting to obtain the target transaction data, specifically a personal computer, a smart phone, a tablet computer and the like.

[0083] In the related art, when generating an electronic contract, the method adopted is that the application side obtains data from the server side and renders and generates the electronic contract based on the obtained data. However, there is a situation where the performance of the application side is insufficient, resulting in the failure of electronic contract generation, affecting the user's transaction processing and causing inconvenience to the user.

[0084] In the embodiment of the present specification, the server 10 obtains template generation data set for a preset transaction type transmitted by the user 20 as required, obtains the transaction identifier and static data of the preset transaction type in the template generation data, obtains the dynamic fields and field identifiers in the template generation data, configures target field parameters corresponding to the dynamic fields, the target field parameters including data acquisition rules and data protection rules, and then generates a target transaction data template corresponding to the preset transaction type based on the static data and dynamic fields. The server 10 stores the target transaction data template in the database 30 based on the transaction identifier and stores the dynamic fields in the database 30 based on the field identifier. When the server 10 receives a request transmitted by the application 40, the server 10 generates target transaction data based on the target transaction data template read from the database 30 and transmits the target transaction data to the application 40. The parameters of the dynamic fields in the transaction template are customized as required. By pre-storing the generated target transaction data template, it is convenient to subsequently generate corresponding target transaction data for the preset transaction type, thereby improving the convenience of users generating transaction templates. Generating transaction data based on the target transaction data template improves the efficiency of transaction processing.

[0085] based on Figure 1 The system architecture shown below will be combined with Figure 2-Figure 5 , a detailed introduction to the transaction processing method provided in the embodiments of this specification is given.

[0086] See Figure 2 , provides a flow chart of a transaction processing method according to the embodiment of this specification. Figure 2As shown, the method of the embodiment of this specification may include the following steps S102 to S108.

[0087] S102, obtaining template generation data corresponding to a preset transaction type, and obtaining a transaction identifier and static data of the preset transaction type in the template generation data;

[0088] In one embodiment, template generation data set for a preset transaction type input by a user to a server is obtained. The preset transaction type can be any type of transaction, for example, a transaction such as activating a password-free payment function. The template generation data can be data involved in generating a transaction template corresponding to the preset transaction type. The template generation data is parsed to obtain a transaction identifier and static data corresponding to the preset transaction type included in the template generation data. The transaction identifier can be an identifier used to characterize the preset transaction type, for example, a transaction name, or a code for the transaction type. The static data can be data included in the template generation data and used to generate fixed text in the transaction template, for example, text data corresponding to fixed regulations, precautions, etc.

[0089] S104, obtaining dynamic fields and field identifiers in the template generated data, and configuring target field parameters corresponding to the dynamic fields;

[0090] In one embodiment, dynamic fields included in the template-generated data and corresponding field identifiers are obtained. A dynamic field may be a field whose content, attributes, or display mode can dynamically change based on runtime conditions, user input, data changes, and other factors. Specifically, it may be a field used to populate transaction-related data when generating transaction data corresponding to a transaction type. The field identifier may be an identifier used to characterize the dynamic field. It is understood that since the template-generated data may include multiple dynamic fields, each dynamic field is labeled according to its field identifier to distinguish them. Since transaction types and dynamic fields are associated, a correlation between the field identifier and the transaction identifier is established to facilitate subsequent search for relevant information related to the dynamic field corresponding to the transaction type. For each dynamic field, target field parameters corresponding to the dynamic field are then configured based on the content included in the template-generated data. The target field parameters may include data acquisition rules and data protection rules. The data acquisition rules may indicate how to acquire the data corresponding to the dynamic field. The data protection rules may indicate how to protect the acquired data in the dynamic field, such as data masking or data encryption.

[0091] S106, generating a target transaction data template corresponding to a preset transaction type based on the static data and the dynamic fields;

[0092] In one embodiment, a target transaction data template corresponding to a preset transaction type is generated based on the acquired static data and dynamic fields. The target transaction data template can be used to generate target transaction data corresponding to the preset transaction type. The target transaction data can be data for handling a transaction, such as a contract to be signed. It is understood that the target transaction data template is a template used to standardize the structured definition of data to ensure consistency, accuracy, and completeness of the transaction data during storage, transmission, and processing. Specifically, it can include data such as the transaction item of the preset transaction type, the transaction number, and additional information.

[0093] S108, storing the target transaction data template based on the transaction identifier, and storing the dynamic field based on the field identifier;

[0094] In one embodiment, a target transaction data template corresponding to a preset transaction type is stored based on a transaction identifier of the preset transaction type, and dynamic fields are stored based on a field identifier. It should be noted that due to the correlation between the transaction identifier and the field identifier, the field identifiers of the dynamic fields in the target transaction data template corresponding to the transaction identifier can be found based on the transaction identifier, and the dynamic fields and the target field parameters corresponding to each dynamic field can be obtained based on the field identifier. This facilitates obtaining the stored target transaction data template based on the transaction identifier and field identifier, thereby generating the desired target transaction data.

[0095] In an embodiment of the present specification, data is generated according to the acquired template, transaction identifiers and static data, as well as dynamic fields and field identifiers are obtained, and after parameter configuration of the dynamic fields, a target transaction template corresponding to the transaction identifier is generated, so that the parameters of the dynamic fields in the transaction template can be customized according to needs, and by pre-storing the generated target transaction data template, it is convenient to subsequently generate corresponding target transaction data for preset transaction types, thereby improving the convenience of users generating transaction templates, and generating transaction data according to the target transaction data template, thereby improving the efficiency of transaction processing.

[0096] See Figure 3 , provides a flow chart of a transaction processing method according to the embodiment of this specification. Figure 3 As shown, the method of the embodiment of this specification may include the following steps S202 to S218.

[0097] S202, obtaining template generation data corresponding to a preset transaction type, and obtaining a transaction identifier and static data of the preset transaction type in the template generation data;

[0098] In one embodiment, template generation data set for a preset transaction type input by a user to the server is obtained. The preset transaction type can be any type of transaction, for example, it can be a transaction such as activating a password-free payment function. The template generation data can be data involved in generating a transaction template corresponding to the preset transaction type. The data type of the template generation data can be set according to actual conditions, for example, it can be an html file, etc. The template generation data is parsed to obtain the transaction identifier and static data corresponding to the preset transaction type included in the template generation data. The transaction identifier can be an identifier used to characterize the preset transaction type, for example, it can be a transaction name, or a code for the transaction type, etc. The static data can be data included in the template generation data, used to generate fixed text in the transaction template, for example, it can be text data corresponding to fixed regulations, precautions, etc.

[0099] S204, obtaining the dynamic fields in the template generated data, as well as the field identifiers and field types corresponding to the dynamic fields;

[0100] In one embodiment, the dynamic fields included in the template-generated data, along with the field identifiers and field types corresponding to the dynamic fields, are obtained. A dynamic field may be a field whose content, attributes, or display mode can dynamically change based on factors such as runtime conditions, user input, and data changes. Specifically, it may be a field used to enter transaction-related data when generating transaction data corresponding to a transaction type. The field identifier may be an identifier used to characterize the dynamic field. The field type may indicate the type of data to be entered into the dynamic field, such as the names of the transaction parties, identification data, or other data types.

[0101] It is understood that since the template-generated data may include multiple dynamic fields, each dynamic field is labeled according to a field identifier to distinguish them. Since transaction types are associated with dynamic fields, an association between field identifiers and transaction identifiers is established to facilitate subsequent search for relevant information about the dynamic fields corresponding to the transaction type.

[0102] For example, if the preset transaction type is credit card processing, and the dynamic fields involved include user name, ID data, and address data, the transaction identifier could be "Credit Card Processing," and the field identifiers could be "Credit Card Processing - User Name," "Credit Card Processing - ID Data," or "Credit Card Processing - Address Data." If the transaction identifier is "A," then user name, ID data, and address data are the first three dynamic fields in the dynamic field order, and the corresponding field identifiers are "A1," "A2," and "A3," respectively. The specific naming method for transaction identifiers and field identifiers can be set based on actual circumstances.

[0103] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, storage, and display, etc.), and signals involved in the embodiments of this specification are all authorized by the user or fully authorized by all parties, and the collection, use, and processing of relevant data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, the dynamic data such as certificate data and address data involved in this specification are all obtained with full authorization.

[0104] S206, determining the data source corresponding to the field type, and configuring data acquisition rules corresponding to the field identifier based on the data source;

[0105] In one embodiment, a data source corresponding to the field type of a dynamic field is determined, and data acquisition rules corresponding to the field identifier are configured based on the data source and a data interface supported by the server. The data source may be a data source device, such as a system, database, or platform, that stores data corresponding to the field type for filling in the dynamic field. The data interface may be an interface on the server for connecting to the data source. The data acquisition rules may indicate a method for acquiring dynamic data corresponding to the field identifier from the data source. The dynamic data may be data acquired from the data source for filling in the dynamic field.

[0106] Specifically, the data acquisition rule may include the data source corresponding to the field identifier, the data interface connected to the data source in the server, and the method of generating the data acquisition request, etc., which are related contents for acquiring dynamic data from the data source.

[0107] S208, determining the sensitivity level corresponding to the field type based on the field type and the preset transaction type;

[0108] In one embodiment, a sensitivity level corresponding to the dynamic field type is determined based on the field type and the preset transaction type. The sensitivity level may represent the importance of confidentiality to the data associated with the dynamic field in the preset transaction type. The higher the sensitivity level, the more important confidentiality is to the dynamic field.

[0109] S210, if the sensitivity level indicates that the field type is a sensitive field, configuring a desensitization rule corresponding to the dynamic field based on the field type;

[0110] In one embodiment, a determination is made as to whether the field type is a sensitive field based on the sensitivity of the dynamic field. If the sensitive field indicates that the field type is a sensitive field, a desensitization rule corresponding to the dynamic field is configured based on the field type. The desensitization rule may indicate a method for desensitizing dynamic data.

[0111] Specifically, the method for determining whether a dynamic field is a sensitive field based on the sensitivity level can be: comparing the sensitivity level of the dynamic field with a preset sensitivity threshold; if the sensitivity level is greater than or equal to the sensitivity threshold, the field type of the dynamic field is considered to be a sensitive field; if the sensitivity level is less than the sensitivity threshold, the field type of the dynamic field is considered to be a non-sensitive field.

[0112] Exemplarily, desensitizing dynamic data according to desensitizing rules can be performed by hiding, deforming, or replacing the dynamic data according to preset desensitizing rules, ensuring that only authorized users can access complete and authentic data, while other users only see processed data. Specifically, desensitizing dynamic data can be performed by using fixed value replacement, data masking, data generalization, etc. Fixed value replacement can be replacing dynamic data with preset fixed values, such as replacing a name with "Mr. A" or a phone number with "12345654321." Masking data can be masking part or all of the dynamic data with symbols such as "*." Data generalization can be desensitizing numerical dynamic data, such as generalizing "8000" to "3000-10000." The data desensitization method used by the desensitization rules can be set according to actual circumstances.

[0113] For example, Figure 4 As shown, Figure 4 The data is desensitized by replacing fixed values, replacing the name "Zhang San" with the fixed value "Mr. Jia", the phone number "12345678900" with the fixed value "12345654321", and the address information "AA Province BB City" with "a certain place", thereby desensitizing the dynamic parameters.

[0114] For example, it can also be Figure 5 As shown, Figure 5 The data is desensitized by shielding the data. The text except the surname in the name "Zhang San" is shielded to obtain "Zhang*", the fifth to eighth digits in the phone number "12345678900" are shielded to obtain "123****8900", and the city in the address information "AA Province BB City" is shielded to obtain "AA Province ** City", thereby achieving data desensitization of dynamic parameters.

[0115] It should be noted that the masking rules for the same field type can vary for different transaction types. For example, for transaction type A, the phone number is a sensitive field, so you need to configure a corresponding rule for this dynamic field to mask the data. However, for transaction type B, the phone number is not a sensitive field, so you don't need to configure a data masking rule for this dynamic field. You can set this up based on your actual situation.

[0116] S212, configuring a first encryption rule corresponding to the field identifier based on the field type and the preset transaction type;

[0117] In one embodiment, the security importance of the dynamic data corresponding to the field identifier is determined based on the field type and the preset transaction type, and a first encryption rule corresponding to the field identifier is configured based on the security importance. The first encryption rule is used to encrypt the dynamic data corresponding to the dynamic field, and the encrypted dynamic data is placed in a locked state. It will be understood that data in the 'locked' state only supports read operations before authorization verification, maintaining the data content unchanged, thereby ensuring the security of the encrypted dynamic data.

[0118] Specifically, the configured first encryption rule can be configured to encrypt dynamic data, such as using symmetric encryption or asymmetric encryption. Symmetric encryption requires the same key for encryption and decryption, while asymmetric encryption uses a public key for encryption and a private key for decryption. The specific setting can be determined based on actual circumstances.

[0119] It should be noted that, similar to configuring desensitization rules, for each dynamic data, the corresponding first encryption rule can be set according to the transaction type and field type. For dynamic data with lower security importance, desensitization or encryption processing can be omitted to improve data processing efficiency by reducing the amount of data processing and reduce unnecessary computing resource loss.

[0120] S214, generating a target transaction data template corresponding to a preset transaction type based on the static data and the dynamic fields;

[0121] In one embodiment, a target transaction data template corresponding to a preset transaction type is generated based on the acquired static data and the dynamic fields configured with the target dynamic parameters. The target transaction data template can be used to generate target transaction data corresponding to the preset transaction type. It is understood that the target transaction data template is a structured definition used to standardize data to ensure consistency, accuracy, and completeness of transaction data during storage, transmission, and processing. Specifically, it can include data such as the transaction item, transaction number, and additional information of the preset transaction type.

[0122] Furthermore, after generating the target transaction data template, in addition to configuring the first encryption rule for the dynamic fields in the target transaction data template, a second encryption rule corresponding to the target transaction data template can also be configured based on a preset transaction type. The second encryption rule can be used to encrypt the target transaction data corresponding to the target transaction data template to improve the security of the target transaction data generated based on the target transaction data template. The specific encryption method of the second encryption rule can be referenced to the first encryption rule and is not further described here.

[0123] It should be noted that the first encryption rule configured for the dynamic field and the second encryption rule configured for the target transaction data template can be executed simultaneously when the target transaction data template is called, or any one of them can be selected for execution. The specific settings can be made according to actual conditions.

[0124] S216, storing the target transaction data template in the first database based on the transaction identifier;

[0125] In one embodiment, after the target transaction data template corresponding to the preset transaction data is generated, the target transaction data template is stored in a first database based on the transaction identifier, so that the target transaction data template can be subsequently retrieved from the first database based on the transaction identifier. The first database can be a database corresponding to the server or a cloud database of a server cluster to which the server belongs, and the specific setting can be based on actual circumstances.

[0126] Furthermore, in order to improve the efficiency of searching for the target transaction data template, a feasible approach is to store the target transaction data template in the first database of the server based on the transaction identifier, and in the cluster cache space corresponding to the server cluster to which the server belongs. Among them, the data reading priority of the cluster cache space is higher than that of the first database. The cluster cache space can be a cache space shared by the server cluster, and each server in the server cluster can directly read the target transaction data template in the cluster cache space. It is understandable that since the data reading efficiency in the cluster cache space is higher than the efficiency of reading data in the first database, the data reading priority of the cluster cache space is higher than that of the first database. If the target transaction data template is not read in the cluster cache space, it will be read in the first database.

[0127] Furthermore, when storing the target transaction data template in the first database and the cluster cache space, a transaction signing method corresponding to the generated transaction identifier can also be generated. Based on the transaction identifier, the transaction signing method and the target transaction data template are stored in the first database of the server, and in the cluster cache space corresponding to the server cluster to which the server belongs, so that when the target transaction data template is subsequently obtained, the corresponding transaction signing method can be obtained at the same time. The transaction signing method can be used to indicate the display method of the target transaction data corresponding to the target transaction data template, for example, it can indicate the display duration of the target transaction data. It is understandable that since the transaction signing method is related to the display method of the target transaction data, when the target transaction data is transmitted to the server, the transaction signing method needs to be transmitted synchronously so that the server displays the target transaction data according to the transaction signing method. Therefore, storing the target transaction data template and the transaction signing behavior based on the transaction identifier can improve the search efficiency of the transaction signing behavior.

[0128] It should be noted that a preset transaction type can correspond to one target transaction data template or multiple target transaction data templates. Therefore, by storing the target transaction data template based on the transaction identifier of the preset transaction type, all target transaction data templates corresponding to the preset transaction type can be obtained simultaneously based on the transaction identifier in the future.

[0129] Furthermore, if the cluster cache space or the first database corresponding to the server stores a historical transaction data template corresponding to the transaction identifier, the target transaction data template is updated with the historical transaction data template. The historical transaction data template can be a transaction data template previously stored in the cluster cache space or the first database.

[0130] S218, based on the field identifier and the transaction identifier, storing the target field parameter of the dynamic field in the second database and the local cache space of the server;

[0131] In one embodiment, after configuring the target field parameters for each dynamic field in the target transaction data template, the target field parameters of the dynamic field are stored in a second database and a local cache space on the server based on the field identifier and the transaction identifier. The local cache space can be a cache space used by the server to store temporary data, and the data reading priority of the local cache space is higher than that of the second database. The second database can be a database used to store field parameters. The second database can be the same database as the first database or a different database from the first database. In order to improve the reading efficiency of the target field parameters, the second database can be encapsulated, and the specific encapsulation method can be set according to actual conditions.

[0132] Furthermore, if the historical field parameters corresponding to the field identifier are stored in the local cache space or the second database, the target field parameters are updated with the historical field parameters. The historical field parameters can be field parameters stored in advance in the local cache space or the second database. It should be noted that since the data in the local cache space is temporary data, if the server performs a restart or shutdown and then restart behavior, it is necessary to read the target field parameters in the second database and cache them in the local cache space. The reading time can be executed when the server is started, or when the target transaction data template is called. The specific setting can be made according to the actual situation.

[0133] It should be noted that the trigger method for updating the target transaction data template and target field parameters can be to update them at fixed time intervals, or to update them when changes are detected in the data used to generate the target transaction data template or target field parameters, so that the target transaction data template and target field parameters can be updated in a timely manner.

[0134] In an embodiment of the present specification, by generating data based on the acquired template, acquiring the transaction identifier and static data, as well as the dynamic field and field identifier, and configuring the parameters of the dynamic field, a target transaction template corresponding to the transaction identifier is generated, so that the parameters of the dynamic field in the transaction template can be customized according to needs, and by pre-storing the generated target transaction data template, it is convenient to subsequently generate corresponding target transaction data for the preset transaction type, thereby improving the convenience of users generating transaction templates, and generating transaction data based on the target transaction data template, thereby improving the efficiency of transaction processing. In addition, by customizing the target field parameters of the dynamic field as needed, the convenience of configuring the field parameters of the dynamic field is improved, thereby improving the convenience and practicality of creating the target transaction data template. Further, the target transaction data template and target field parameters are stored in the cache space according to the transaction identifier and field identifier, and updated in real time, thereby improving the reading convenience and accuracy of the target transaction data template and target field parameters, thereby improving the reliability of generating target transaction data based on the target transaction data template and target field parameters.

[0135] See Figure 6 , provides a flow chart of a transaction processing method according to the embodiment of this specification. Figure 6 As shown, the method of the embodiment of this specification may include the following steps S302 to S310.

[0136] S302, if the server receives a transaction data generation request transmitted by the application, then determines the transaction type in the transaction data generation request;

[0137] In one embodiment, if a server receives a transaction data generation request transmitted by an application, the server parses the transaction data generation request and determines the transaction type in the transaction data generation request. The transaction data generation request may be data generated by the application and transmitted to the server, requesting the server to generate transaction data. The transaction data generation request may include the data type of the transaction data to be generated, as well as the account identifier used by the application. The transaction type may represent the type of transaction requested by the user on the application, such as a transaction requesting the activation of a password-free payment function.

[0138] S304: If the transaction type is a preset transaction type, obtain a target transaction data template corresponding to the preset transaction type, and obtain target field parameters corresponding to dynamic fields in the target transaction data template;

[0139] In one embodiment, the transaction type is matched with the type stored in the server. If the transaction type matches the preset transaction type, a search is performed in the cluster cache space or the first database in the server based on the transaction identifier of the transaction type to obtain the target transaction data template corresponding to the preset transaction type, and a search is performed in the local cache space or the second database of the server based on the field identifier of the dynamic field in the target transaction data template to obtain the target field parameters corresponding to the dynamic field. The target transaction data template can be a pre-stored template for generating target transaction data corresponding to the transaction identifier. The target field parameters include data acquisition rules and data protection rules. The data acquisition rules can be a method for indicating how to obtain data corresponding to the dynamic field. The data protection rules can be a method for indicating how to protect the data of the acquired dynamic field, such as data desensitization, data encryption, etc.

[0140] S306, acquiring dynamic data corresponding to the dynamic field based on the data acquisition rules and data protection rules corresponding to the target field parameters;

[0141] In one embodiment, based on the data interface indicated by the data acquisition rule corresponding to the target field parameter, the data corresponding to the dynamic field is obtained, and then the acquired data is desensitized and / or encrypted according to the data protection rule of the dynamic field to obtain the dynamic data corresponding to the dynamic field.

[0142] S308, generating target transaction data corresponding to the transaction data generation request based on the dynamic data and the static data in the target transaction data template;

[0143] In one embodiment, target transaction data corresponding to the transaction data generation request is generated based on the static data in the target transaction data template and the acquired dynamic data is entered into the dynamic fields of the target transaction data template. The static data may be fixed text data included in the target transaction data template, such as text data corresponding to fixed regulations, notes, etc. The target transaction data may be transaction processing data, such as a contract to be signed, a user's transaction processing certificate, etc.

[0144] S310, transmitting the target transaction data to the application end so as to display the target transaction data on the application end;

[0145] In one embodiment, based on the data transmission channel for the application end to transmit the transaction data generation request to the server end, the generated target transaction data is transmitted to the application end, and the target transaction data is displayed on the application end, so that the user can handle the transaction according to the displayed target transaction data.

[0146] It should be noted that, since the target transaction data has been rendered in the server, after receiving the target transaction data, the application only needs to display the target transaction data on the display interface of the application.

[0147] In an embodiment of the present specification, a target transaction data template is obtained through a transaction identifier, and target field parameters are obtained based on the field identifier of the dynamic field of the target transaction data template. The target field parameters are used to obtain dynamic data corresponding to the dynamic field, and target transaction data is generated based on the static data in the target transaction data template. The rendered target transaction data is transmitted to the application end for display, thereby generating target transaction data based on the computing resources of the server end through the target transaction data template. This can not only avoid transaction processing failures caused by insufficient computing power on the application end, but also avoid data leakage during transmission, thereby improving the efficiency, reliability and security of target transaction data generation.

[0148] See Figure 7 , provides a flow chart of a transaction processing method according to the embodiment of this specification. Figure 7 As shown, the method of the embodiment of this specification may include the following steps S402 to S422.

[0149] S402, if the server receives the transaction data generation request transmitted by the application, then determines the transaction type in the transaction data generation request;

[0150] In one embodiment, if a server receives a transaction data generation request transmitted by an application, the server parses the transaction data generation request and determines the transaction type in the transaction data generation request. The transaction data generation request may be data generated by the application and transmitted to the server, requesting the server to generate transaction data. The transaction data generation request may include the data type of the transaction data to be generated, as well as the account identifier used by the application. The transaction type may represent the type of transaction requested by the user on the application, such as a transaction requesting the activation of a password-free payment function.

[0151] S404: If the transaction type is a preset transaction type, obtain a transaction identifier of the preset transaction type, and obtain a target transaction data template from the cluster cache space corresponding to the server or the first database based on the transaction identifier;

[0152] In one embodiment, the transaction type is matched with the type stored in the server. If the transaction type matches the preset transaction type, the cluster cache space or the first database in the server is searched based on the transaction identifier of the transaction type to obtain the target transaction data template corresponding to the preset transaction type. The transaction identifier can be an identifier used in the transaction data generation request to characterize the transaction type corresponding to the transaction to be processed, such as the transaction name, or the code of the transaction type. The cluster cache space can be a cache space shared by a server cluster. The first database can be a database corresponding to the server, or it can be a cloud database of the server cluster to which the server belongs, and can be set according to actual conditions. The target transaction data template can be a pre-stored template for generating target transaction data corresponding to the transaction identifier.

[0153] Specifically, the method for obtaining the target transaction data template based on the transaction identifier can be: based on the transaction identifier, the identifiers of the transaction data templates included in the cluster cache space corresponding to the server are matched; if a matching transaction data template exists, the transaction data template is determined as the target transaction data template. If the cluster cache space does not include a transaction data template that matches the transaction identifier, a search is performed in the first database based on the transaction identifier to obtain the target transaction data template that matches the transaction identifier. It is understandable that because the cluster cache space has a higher read efficiency than the first database, the data read priority of the cluster cache space is set higher than that of the first database to improve the efficiency of obtaining the target transaction data template.

[0154] S406, parsing the target transaction data template to obtain static data and dynamic fields in the target transaction data template;

[0155] In one embodiment, the target transaction data template is parsed to obtain static data and dynamic fields in the target transaction data template. The static data may be data included in the template generation data and used to generate fixed text in the transaction template, such as text data corresponding to fixed regulations, notes, etc. The dynamic fields may be fields in the target transaction data template whose content, attributes, or display mode can be dynamically changed based on factors such as runtime conditions, user input, and data changes. Specifically, they may be fields used to enter transaction-related data when generating transaction data corresponding to a transaction type.

[0156] S408, based on the field identifier of the dynamic field, obtaining the target field parameter corresponding to the field identifier in the local cache space of the server or the second database;

[0157] In one embodiment, a field identifier corresponding to a dynamic field is obtained, and based on the field identifier, a search is performed in the server's local cache space or a second database to obtain target field parameters that match the field identifier. The local cache space can be a cache space used by the server to store temporary data. The second database can be a database used to store field parameters. The second database can be the same database as the first database or a different database from the first database. To improve the reading efficiency of the target field parameters, the second database can be encapsulated, and the specific encapsulation method can be set according to actual conditions.

[0158] The target field parameters may be parameters configured for the dynamic fields, so that the dynamic fields are filled and protected according to the target field parameters, thereby obtaining the target transaction data corresponding to the target transaction data template.

[0159] Specifically, the method for obtaining the target field parameter based on the field identifier can be: matching the identifiers of the various field parameters included in the local cache space corresponding to the field identifier on the server side, and if there is a matching field parameter, then determining the field parameter as the target field parameter. If the local cache space does not include a field parameter that matches the field identifier, then searching in the second database based on the field identifier to obtain the target field parameter that matches the field identifier. It can be understood that since the reading efficiency of the local cache space is higher than that of the second database, the data reading priority of the local cache space is higher than that of the second database to improve the efficiency of obtaining the target field parameter.

[0160] It should be noted that, due to the correlation between the transaction identifier and the field identifier, even if different transaction data templates may include the same dynamic field type, the target field parameters can be accurately found in the local cache space or the second database based on the field identifier.

[0161] S410, determining a data acquisition interface corresponding to the dynamic field in the server based on a data acquisition rule corresponding to the target field parameter;

[0162] In one embodiment, a data acquisition rule is obtained from the target field parameters of a dynamic field, and a data acquisition interface for acquiring data on the server side is determined based on the data acquisition rule. The data acquisition rule may indicate a method for acquiring data corresponding to the dynamic field. Specifically, the data acquisition rule may include information related to acquiring dynamic data from the data source, including the data source corresponding to the field identifier, the data interface on the server side that connects to the data source, and the method for generating a data acquisition request. The data source may be a data source device such as a system, database, or platform that stores data corresponding to the field type used to populate the dynamic field. The data interface may be an interface on the server side that connects to the data source.

[0163] It should be noted that the data acquisition interface may be a data transmission interface in the server for connecting to a data source, and may specifically be a connection interface at the hardware level or a protocol interface at the software level.

[0164] S412, searching in the data source corresponding to the data acquisition interface to obtain dynamic data corresponding to the dynamic field;

[0165] In one embodiment, a data transmission channel is established between the server and the data source based on a data acquisition interface. The data source is searched based on the field type to retrieve dynamic data corresponding to the dynamic field. The dynamic data can be data used to populate the dynamic field, providing the dynamic field with substantive content. The data type of the dynamic data can be text data, image data, or the like, and can be set based on actual circumstances.

[0166] Specifically, the method for obtaining dynamic data from the data source can be to perform data search based on the field type and the user identifier of the application end, and obtain the dynamic data belonging to the field type corresponding to the user identifier in the data source. The user identifier can be included in the transaction data generation request transmitted by the application end, and is used to represent the identifier of the user applying for the transaction, for example, it can be the user's account information. It can be understood that the data acquisition interface corresponds to the data source. If the data source indicated by the data acquisition rules included in the target field parameters of different dynamic fields is the same, then the method of calling the data acquisition interface to obtain dynamic data can be called in sequence according to the arrangement order of the dynamic fields in the target transaction data template, and can be set according to actual conditions.

[0167] Dynamic data can be data obtained from a data source and used to populate dynamic fields. For example, if the field type of a dynamic field is "Home Address" and the field identifier is "Credit Card Application - Home Address," the data acquisition interface is called to retrieve the dynamic data stored in the data source for the user identifier "AA Province BB City CC District DD Street EE Number" and populate the dynamic data into the dynamic field corresponding to the field identifier "Credit Card Application - Home Address." The user identifier can be included in the transaction data generation request transmitted by the application, indicating the user to be processed, such as the user's account number.

[0168] For example, if the field type is name, the data acquisition interface is called to obtain the name of the user corresponding to the user ID, "Zhang San", from the corresponding data source. If the field type is phone number, the data acquisition interface is called to obtain the registered phone number "12345678900" of the user corresponding to the user ID from the corresponding data source. If the field type is address information, the data acquisition interface is called to obtain the registered home address of the user corresponding to the user ID, "AA Province BB City CC District DD Street EE Number", etc., from the corresponding data source.

[0169] The data source can be a system, platform, or database connected to the server. It should be noted that to ensure data security, the server only receives transaction data requests from the application and does not obtain other data from the application. This prevents data leakage during the server's acquisition of dynamic data from the application, which could lead to unnecessary security risks. The data source can be a device connected to the server via a data acquisition interface or on the same local area network, thereby reducing the probability of data leakage during the server's acquisition of dynamic data and improving the security of dynamic data acquisition.

[0170] S414: If the dynamic field is a sensitive field, desensitize the dynamic data based on the desensitization rule in the data protection rule to obtain desensitized dynamic data, and determine the desensitized dynamic data as the dynamic data corresponding to the dynamic field;

[0171] In one embodiment, after obtaining the dynamic data of the dynamic field, the desensitization rules in the data protection rules included in the target field parameters of the dynamic field are determined. If the desensitization rules indicate that the dynamic data needs to be desensitized, the dynamic data is desensitized using the data desensitization method indicated by the desensitization rules to obtain the desensitized dynamic data, and the desensitized dynamic data is determined as the dynamic data corresponding to the dynamic field.

[0172] Specifically, the data desensitization method can be fixed value replacement, data shielding, data generalization, etc. The specific process of desensitizing dynamic data according to the data desensitization method can refer to the relevant content of step S210, which will not be repeated here.

[0173] S416 , generating target transaction data corresponding to the transaction data generation request based on the dynamic data and the static data in the target transaction data template;

[0174] In one embodiment, target transaction data corresponding to the transaction data generation request is generated based on the static data in the target transaction data template and by filling the acquired dynamic data into the dynamic fields of the target transaction data template. The static data may be fixed text data included in the target transaction data template, such as text data corresponding to fixed regulations, notes, etc. The target transaction data may be transaction processing data, such as a contract to be signed, a user's transaction processing certificate, etc.

[0175] For example, Figure 8 As shown, Figure 8 The dynamic fields in the target transaction data template are in a blank state waiting to be input, and after filling each dynamic data into the corresponding dynamic field according to the field identifier, the target transaction data corresponding to the transaction data generation request is obtained.

[0176] S418, obtaining a transaction signing method corresponding to the target transaction data based on the preset transaction type, and a target encryption method corresponding to the preset transaction type;

[0177] In one embodiment, a search is performed in the cluster cache space or the first database based on the transaction identifier to obtain a transaction signing method corresponding to the transaction type and a target encryption method corresponding to the preset transaction type. The transaction signing method may be a display method for indicating the target transaction data corresponding to the target transaction data template, such as the display duration of the target transaction data. The target encryption method may be a method for encrypting the target transaction data.

[0178] Specifically, the target encryption method may include a first encryption rule for encrypting dynamic data in the target transaction data and a second encryption rule for encrypting the target transaction data.

[0179] Furthermore, in addition to the transaction signing method, the data generated for the target transaction data may also include transaction flow, electronic signatures, and the like. The transaction flow can be used to represent the response process to the transaction data generation request, and may specifically include data such as the user ID, the time the transaction data generation request was generated, and the processing status. The electronic signature can be used to record the processing progress of the target transaction data, and may specifically include data such as the user ID, transaction processing progress, transaction processing time, and data storage time. Other included data can be configured based on actual circumstances.

[0180] S420, encrypting the target transaction data and / or dynamic data in the target transaction data based on the target encryption method to obtain encrypted target transaction data;

[0181] In one embodiment, based on the first encryption rule and the second encryption rule in the obtained target encryption method, a determination is made as to whether to encrypt the dynamic data and the target transaction data in the target transaction data. If necessary, encryption is performed according to the target encryption method to obtain the encrypted target transaction data. The first encryption rule and the second encryption rule may be configured to encrypt the dynamic data, such as using symmetric encryption or asymmetric encryption. Symmetric encryption requires the use of the same key for encryption and decryption, while asymmetric encryption uses a public key for encryption and a private key for decryption. The specific encryption method used can be set according to actual circumstances.

[0182] Specifically, the method for obtaining the encrypted target transaction data may be: encrypting the dynamic data in the target transaction data based on the first encryption rule corresponding to the field identifier of the dynamic data, and / or encrypting the target transaction data based on the second encryption rule corresponding to the preset transaction type. If the first encryption rule corresponding to the field identifier of the dynamic data indicates that the dynamic data is encrypted, the dynamic data is processed according to the encryption method of the first encryption rule. If the second encryption rule corresponding to the transaction identifier indicates that the target transaction data needs to be encrypted, the target transaction data is encrypted according to the encryption method in the second encryption rule to obtain the encrypted target transaction data. The encrypted dynamic data is in a locked state. It can be understood that data in a 'locked' state only supports read operations before authorization verification, maintains the data content constant, and thus can ensure the security of the encrypted dynamic data.

[0183] It is understandable that dynamic data and target transaction data can be encrypted at the same time, or only dynamic data or target transaction data can be encrypted, specifically by setting the corresponding first encryption rule and second encryption rule according to actual conditions when creating the target transaction data template.

[0184] Optionally, since the first encryption rule may be the content included in the data protection rule in the target field parameter corresponding to the dynamic field, after obtaining the first encryption rule from the local cache space or the second database, the dynamic data is encrypted according to the first encryption rule to obtain the encrypted dynamic data, without the need to encrypt after generating the target transaction data. The specific time for encrypting the dynamic data can be set according to actual conditions.

[0185] For example, Figure 9 As shown, Figure 9 The figure shows the encrypted target transaction data obtained by encrypting dynamic data using the data shielding method in the first encryption rule. In the encrypted target transaction data, the name "Zhang San" is encrypted as "Zhang*", the phone number "12345678900" is encrypted as "123****8900", and the home address "DD Street, EE No., CC District, BB City, AA Province" is encrypted as "** Street, ** No., ** District, BB City, AA Province".

[0186] S422, transmitting the encrypted target transaction data and the transaction signing method to the application end, so that the application end displays the encrypted target transaction data based on the transaction signing method;

[0187] In one embodiment, a data transmission channel is created based on a request to transmit transaction data from an application end to a server end, and the encrypted target transaction data and the transaction signing method corresponding to the transaction identifier are transmitted to the application end, so that the application end displays the encrypted target transaction data based on the data display method in the transaction signing method.

[0188] For example, if the target transaction data is a transaction contract, the transaction signing method can include a minimum reading time. During the minimum reading time, the target transaction data and a countdown to the minimum reading time are displayed on the application's display interface, so that the user has a good reading experience of the target transaction data. The specific method of displaying the target transaction data on the application side can be set according to actual circumstances.

[0189] Furthermore, in order to determine the processing progress of the target transaction data, a feasible approach is to monitor the user's processing operations on the target transaction data on the application side in real time, and improve the electronic signature and transaction flow corresponding to the transaction identifier based on the processing operations, so that the management personnel can determine the processing progress of the transaction corresponding to the transaction data generation request, and then assist the user to handle it according to the processing progress, thereby improving the user's transaction processing experience.

[0190] In an embodiment of the present specification, a target transaction data template is obtained through a transaction identifier, and target field parameters are obtained based on the field identifier of the dynamic field of the target transaction data template. The target field parameters are used to obtain dynamic data corresponding to the dynamic field, and target transaction data is generated based on the static data in the target transaction data template. The rendered target transaction data is transmitted to the application end for display, thereby generating target transaction data based on the computing resources of the server end through the target transaction data template. This can not only avoid transaction processing failures due to insufficient computing power on the application end, but also avoid data leakage during data transmission, thereby improving the efficiency, reliability and security of target transaction data generation. Furthermore, by performing data protection actions such as desensitization and encryption on dynamic data, the confidentiality of the generated target transaction data is improved, thereby avoiding data leakage during the transmission of the target transaction data to the application end, and improving the security and reliability of the application end receiving the target transaction data.

[0191] based on Figure 1 The system architecture will be combined with Figure 10 , the transaction processing device provided by the embodiment of this specification is introduced in detail. It should be noted that, Figure 10 The transaction processing device 1 in the present invention is used to execute the transaction processing device 1 in the present invention Figure 2-Figure 5 For the convenience of explanation, only the part related to the embodiment of this specification is shown. For the specific technical details not disclosed, please refer to this specification. Figure 2-Figure 5 The embodiment shown.

[0192] See Figure 10 , is a structural diagram of a transaction processing device provided in the embodiment of this specification. Figure 10 As shown, the transaction processing device 1 of the embodiment of this specification may include: a data acquisition unit 11, a configuration unit 12, a template generation unit 13 and a storage unit 14.

[0193] A data acquisition unit 11 is configured to acquire template generation data corresponding to a preset transaction type, and acquire a transaction identifier and static data of the preset transaction type from the template generation data;

[0194] A configuration unit 12 is configured to obtain dynamic fields and field identifiers in the template-generated data, and configure target field parameters corresponding to the dynamic fields, wherein the target field parameters include data acquisition rules and data protection rules;

[0195] A template generating unit 13 is configured to generate a target transaction data template corresponding to the preset transaction type based on the static data and the dynamic field, wherein the target transaction data template is used to generate target transaction data corresponding to the preset transaction type;

[0196] The storage unit 14 is configured to store the target transaction data template based on the transaction identifier and to store the dynamic field based on the field identifier.

[0197] Optionally, the configuration unit 12 is further configured to:

[0198] Obtaining the dynamic fields in the template-generated data, as well as the field identifiers and field types corresponding to the dynamic fields;

[0199] Determine a data source corresponding to the field type, and configure a data acquisition rule corresponding to the field identifier based on the data source, wherein the data acquisition rule indicates a method for acquiring dynamic data corresponding to the field identifier from the data source;

[0200] Determining a sensitivity level corresponding to the field type based on the field type and the preset transaction type;

[0201] If the sensitivity level indicates that the field type is a sensitive field, configuring a desensitization rule corresponding to the dynamic field based on the field type;

[0202] Based on the field type and the preset transaction type, a first encryption rule corresponding to the field identifier is configured, where the first encryption rule is used to encrypt dynamic data corresponding to the dynamic field, and the encrypted dynamic data is in a locked state.

[0203] Optionally, the template generating unit 13 is further configured to:

[0204] A second encryption rule corresponding to the target transaction data template is configured based on the preset transaction type, where the second encryption rule is used to encrypt the target transaction data corresponding to the target transaction data template.

[0205] Optionally, the storage unit 14 is further configured to:

[0206] Storing the target transaction data template in a first database based on the transaction identifier;

[0207] Based on the field identifier and the transaction identifier, the target field parameter of the dynamic field is stored in the second database and the local cache space of the server. The data reading priority of the local cache space is higher than that of the second database.

[0208] Optionally, the storage unit 14 is further configured to:

[0209] Based on the transaction identifier, the target transaction data template is stored in the first database of the server and in the cluster cache space corresponding to the server cluster to which the server belongs. The data reading priority of the cluster cache space is higher than that of the first database.

[0210] Optionally, the storage unit 14 is further configured to:

[0211] Acquire a transaction signing mode corresponding to the transaction identifier in the template generation data, wherein the transaction signing mode indicates a display mode of target transaction data corresponding to the target transaction data template;

[0212] Based on the transaction identifier, the transaction signing method and the target transaction data template are stored in the first database of the server and in the cluster cache space corresponding to the server cluster to which the server belongs.

[0213] The optional storage unit 14 is further configured to:

[0214] If the historical transaction data template corresponding to the transaction identifier is stored in the cluster cache space corresponding to the server or the first database, the target transaction data template is updated to the historical transaction data template;

[0215] If the local cache space or the second database stores historical field parameters corresponding to the field identifier, the historical field parameters are updated with the target field parameters.

[0216] In an embodiment of the present specification, by generating data based on the acquired template, acquiring the transaction identifier and static data, as well as the dynamic field and field identifier, and configuring the parameters of the dynamic field, a target transaction template corresponding to the transaction identifier is generated, so that the parameters of the dynamic field in the transaction template can be customized according to needs, and by pre-storing the generated target transaction data template, it is convenient to subsequently generate corresponding target transaction data for the preset transaction type, thereby improving the convenience of users generating transaction templates, and generating transaction data based on the target transaction data template, thereby improving the efficiency of transaction processing. In addition, by customizing the target field parameters of the dynamic field as needed, the convenience of configuring the field parameters of the dynamic field is improved, thereby improving the convenience and practicality of creating the target transaction data template. Further, the target transaction data template and target field parameters are stored in the cache space according to the transaction identifier and field identifier, and updated in real time, thereby improving the reading convenience and accuracy of the target transaction data template and target field parameters, thereby improving the reliability of generating target transaction data based on the target transaction data template and target field parameters.

[0217] See Figure 11 , is a structural diagram of a transaction processing device provided in the embodiment of this specification. Figure 11 As shown, the transaction processing device 2 of the embodiment of this specification may include: a type determination unit 21, a template acquisition unit 22, a data acquisition unit 23, a data generation unit 24 and a data transmission unit 25.

[0218] The type determination unit 21 is configured to determine the transaction type in the transaction data generation request if the server receives the transaction data generation request transmitted by the application;

[0219] The template acquisition unit 22 is configured to, if the transaction type is a preset transaction type, acquire a target transaction data template corresponding to the preset transaction type, and acquire target field parameters corresponding to dynamic fields in the target transaction data template;

[0220] A data acquisition unit 23 is configured to acquire dynamic data corresponding to the dynamic field based on a data acquisition rule and a data protection rule corresponding to the target field parameter;

[0221] A data generating unit 24 is configured to generate target transaction data corresponding to the transaction data generation request based on the dynamic data and the static data in the target transaction data template;

[0222] The data transmission unit 25 is configured to transmit the target transaction data to the application end so as to display the target transaction data on the application end.

[0223] Optionally, the template acquisition unit 22 is further configured to:

[0224] Obtaining a transaction identifier of the preset transaction type, and obtaining a target transaction data template from a cluster cache space or a first database corresponding to the server based on the transaction identifier;

[0225] Parsing the target transaction data template to obtain static data and dynamic fields in the target transaction data template;

[0226] Based on the field identifier of the dynamic field, a target field parameter corresponding to the field identifier is acquired in the local cache space of the server or the second database.

[0227] Optionally, the data acquisition unit 23 is further configured to:

[0228] Determining a data acquisition interface corresponding to the dynamic field in the server based on a data acquisition rule corresponding to the target field parameter;

[0229] Searching in the data source corresponding to the data acquisition interface to obtain the dynamic data corresponding to the dynamic field;

[0230] If the dynamic field is a sensitive field, the dynamic data is desensitized based on the desensitization rules in the data protection rules to obtain the desensitized dynamic data, and the desensitized dynamic data is determined as the dynamic data corresponding to the dynamic field.

[0231] Optionally, the data transmission unit 25 is further configured to:

[0232] Acquire, based on the preset transaction type, a transaction signing method corresponding to the target transaction data and a target encryption method corresponding to the preset transaction type;

[0233] encrypting the target transaction data and / or the dynamic data in the target transaction data based on the target encryption method to obtain encrypted target transaction data, wherein the dynamic data in the encrypted target transaction data is in a locked state;

[0234] The encrypted target transaction data and the transaction signing method are transmitted to the application end, so that the application end displays the encrypted target transaction data based on the transaction signing method.

[0235] Optionally, the data transmission unit 25 is further configured to:

[0236] encrypting the dynamic data in the target transaction data based on a first encryption rule corresponding to a field identifier of the dynamic data; and / or

[0237] The target transaction data is encrypted based on a second encryption rule corresponding to the preset transaction type.

[0238] In an embodiment of the present specification, a target transaction data template is obtained through a transaction identifier, and target field parameters are obtained based on the field identifier of the dynamic field of the target transaction data template. The target field parameters are used to obtain dynamic data corresponding to the dynamic field, and target transaction data is generated based on the static data in the target transaction data template. The rendered target transaction data is transmitted to the application end for display, thereby generating target transaction data based on the computing resources of the server end through the target transaction data template. This can not only avoid transaction processing failures due to insufficient computing power on the application end, but also avoid data leakage during data transmission, thereby improving the efficiency, reliability and security of target transaction data generation. Furthermore, by performing data protection actions such as desensitization and encryption on dynamic data, the confidentiality of the generated target transaction data is improved, thereby avoiding data leakage during the transmission of the target transaction data to the application end, and improving the security and reliability of the application end receiving the target transaction data.

[0239] The embodiment of this specification also provides a computer storage medium that can store multiple program instructions, which are suitable for being loaded and executed by a processor as described above. Figures 1-9 The method steps of the embodiment shown, the specific execution process can be found in Figures 1-9 The detailed description of the illustrated embodiment will not be repeated here.

[0240] The embodiment of this specification also provides a computer program product, which stores at least one instruction, and the at least one instruction is loaded and executed by the processor as described above. Figures 1-9 The method steps of the embodiment shown, the specific execution process can be found in Figures 1-9 The detailed description of the illustrated embodiment will not be repeated here.

[0241] See Figure 12 , is a schematic diagram of the structure of an electronic device provided in the embodiment of this specification. Figure 12 As shown, the electronic device 1000 may include: at least one processor 1001, such as a CPU, at least one network interface 1004, an input / output interface 1003, a memory 1005, and at least one communication bus 1002. The communication bus 1002 is used to realize the connection and communication between these components. The network interface 1004 may optionally include a standard wired interface, a wireless interface (such as a WI-FI interface). The memory 1005 may be a high-speed RAM memory, or a non-volatile memory (non-volatile memory), such as at least one disk memory. The memory 1005 may optionally also be at least one storage device located away from the aforementioned processor 1001. As Figure 12 As shown, the memory 1005 as a computer storage medium may include an operating system, a network communication module, an input and output interface module, and a transaction processing application.

[0242] exist Figure 12 In the electronic device 1000 shown, the input / output interface 1003 is mainly used to provide an input interface for the user and obtain data input by the user.

[0243] In one embodiment, the processor 1001 may be configured to call a transaction processing application stored in the memory 1005 and specifically perform the following operations:

[0244] Acquire template generation data corresponding to a preset transaction type, and acquire a transaction identifier and static data of the preset transaction type in the template generation data;

[0245] Acquire dynamic fields and field identifiers in the template-generated data, and configure target field parameters corresponding to the dynamic fields, wherein the target field parameters include data acquisition rules and data protection rules;

[0246] generating a target transaction data template corresponding to the preset transaction type based on the static data and the dynamic field, wherein the target transaction data template is used to generate target transaction data corresponding to the preset transaction type;

[0247] The target transaction data template is stored based on the transaction identifier, and the dynamic field is stored based on the field identifier.

[0248] Optionally, when the processor 1001 obtains the dynamic fields and field identifiers in the template-generated data and configures target field parameters corresponding to the dynamic fields, it specifically performs the following operations:

[0249] Obtaining the dynamic fields in the template-generated data, as well as the field identifiers and field types corresponding to the dynamic fields;

[0250] Determine a data source corresponding to the field type, and configure a data acquisition rule corresponding to the field identifier based on the data source, wherein the data acquisition rule indicates a method for acquiring dynamic data corresponding to the field identifier from the data source;

[0251] Determining a sensitivity level corresponding to the field type based on the field type and the preset transaction type;

[0252] If the sensitivity level indicates that the field type is a sensitive field, configuring a desensitization rule corresponding to the dynamic field based on the field type;

[0253] Based on the field type and the preset transaction type, a first encryption rule corresponding to the field identifier is configured, where the first encryption rule is used to encrypt dynamic data corresponding to the dynamic field, and the encrypted dynamic data is in a locked state.

[0254] Optionally, when executing the generation of the target transaction data template corresponding to the preset transaction type, the processor 1001 specifically performs the following operations:

[0255] A second encryption rule corresponding to the target transaction data template is configured based on the preset transaction type, where the second encryption rule is used to encrypt the target transaction data corresponding to the target transaction data template.

[0256] Optionally, when executing the operation of storing the target transaction data template based on the transaction identifier and storing the dynamic field based on the field identifier, the processor 1001 specifically performs the following operations:

[0257] Storing the target transaction data template in a first database based on the transaction identifier;

[0258] Based on the field identifier and the transaction identifier, the target field parameter of the dynamic field is stored in the second database and the local cache space of the server. The data reading priority of the local cache space is higher than that of the second database.

[0259] Optionally, when executing the operation of storing the target transaction data template in the first database based on the transaction identifier, the processor 1001 specifically performs the following operations:

[0260] Based on the transaction identifier, the target transaction data template is stored in the first database of the server and in the cluster cache space corresponding to the server cluster to which the server belongs. The data reading priority of the cluster cache space is higher than that of the first database.

[0261] Optionally, when executing the operation of storing the target transaction data template in the first database of the server and in the cluster cache space corresponding to the server cluster to which the server belongs based on the transaction identifier, the processor 1001 specifically performs the following operations:

[0262] Acquire a transaction signing mode corresponding to the transaction identifier in the template generation data, wherein the transaction signing mode indicates a display mode of target transaction data corresponding to the target transaction data template;

[0263] Based on the transaction identifier, the transaction signing method and the target transaction data template are stored in the first database of the server and in the cluster cache space corresponding to the server cluster to which the server belongs.

[0264] Optionally, the processor 1001 further performs the following operations:

[0265] If the historical transaction data template corresponding to the transaction identifier is stored in the cluster cache space corresponding to the server or the first database, the target transaction data template is updated to the historical transaction data template;

[0266] If the local cache space or the second database stores historical field parameters corresponding to the field identifier, the historical field parameters are updated with the target field parameters.

[0267] In an embodiment of the present specification, by generating data based on the acquired template, acquiring the transaction identifier and static data, as well as the dynamic field and field identifier, and configuring the parameters of the dynamic field, a target transaction template corresponding to the transaction identifier is generated, so that the parameters of the dynamic field in the transaction template can be customized according to needs, and by pre-storing the generated target transaction data template, it is convenient to subsequently generate corresponding target transaction data for the preset transaction type, thereby improving the convenience of users generating transaction templates, and generating transaction data based on the target transaction data template, thereby improving the efficiency of transaction processing. In addition, by customizing the target field parameters of the dynamic field as needed, the convenience of configuring the field parameters of the dynamic field is improved, thereby improving the convenience and practicality of creating the target transaction data template. Further, the target transaction data template and target field parameters are stored in the cache space according to the transaction identifier and field identifier, and updated in real time, thereby improving the reading convenience and accuracy of the target transaction data template and target field parameters, thereby improving the reliability of generating target transaction data based on the target transaction data template and target field parameters.

[0268] See Figure 13 , is a schematic diagram of the structure of an electronic device provided in the embodiment of this specification. Figure 13 As shown, the electronic device 2000 may include: at least one processor 2001, such as a CPU, at least one network interface 2004, an input / output interface 2003, a memory 2005, and at least one communication bus 2002. The communication bus 2002 is used to realize the connection and communication between these components. The network interface 2004 may optionally include a standard wired interface, a wireless interface (such as a WI-FI interface). The memory 2005 may be a high-speed RAM memory, or a non-volatile memory (non-volatile memory), such as at least one disk memory. The memory 2005 may optionally also be at least one storage device located away from the aforementioned processor 2001. As Figure 13 As shown, the memory 2005 as a computer storage medium may include an operating system, a network communication module, an input and output interface module, and a transaction processing application.

[0269] exist Figure 13 In the electronic device 2000 shown, the input / output interface 2003 is mainly used to provide an input interface for the user and obtain data input by the user.

[0270] In one embodiment, the processor 2001 may be configured to call a transaction processing application stored in the memory 2005 and specifically perform the following operations:

[0271] If the server receives the transaction data generation request transmitted by the application, then determining the transaction type in the transaction data generation request;

[0272] If the transaction type is a preset transaction type, obtaining a target transaction data template corresponding to the preset transaction type, and obtaining a target field parameter corresponding to a dynamic field in the target transaction data template;

[0273] Acquire dynamic data corresponding to the dynamic field based on the data acquisition rule and data protection rule corresponding to the target field parameter;

[0274] generating target transaction data corresponding to the transaction data generation request based on the dynamic data and the static data in the target transaction data template;

[0275] The target transaction data is transmitted to the application end so as to be displayed on the application end.

[0276] Optionally, when the processor 2001 obtains the target transaction data template corresponding to the preset transaction type and parses and obtains the target field parameter corresponding to the dynamic field in the target transaction actual template, it specifically performs the following operations:

[0277] Obtaining a transaction identifier of the preset transaction type, and obtaining a target transaction data template from a cluster cache space or a first database corresponding to the server based on the transaction identifier;

[0278] Parsing the target transaction data template to obtain static data and dynamic fields in the target transaction data template;

[0279] Based on the field identifier of the dynamic field, a target field parameter corresponding to the field identifier is acquired in the local cache space of the server or the second database.

[0280] Optionally, when executing the data acquisition rule and the data protection rule in the target field parameter to acquire the dynamic data corresponding to the dynamic field, the processor 2001 specifically performs the following operations:

[0281] Determining a data acquisition interface corresponding to the dynamic field in the server based on a data acquisition rule corresponding to the target field parameter;

[0282] Searching in the data source corresponding to the data acquisition interface to obtain the dynamic data corresponding to the dynamic field;

[0283] If the dynamic field is a sensitive field, the dynamic data is desensitized based on the desensitization rules in the data protection rules to obtain the desensitized dynamic data, and the desensitized dynamic data is determined as the dynamic data corresponding to the dynamic field.

[0284] Optionally, when executing the operation of transmitting the target transaction data to the application end so as to display the target transaction data on the application end, the processor 2001 specifically performs the following operations:

[0285] Acquire, based on the preset transaction type, a transaction signing method corresponding to the target transaction data and a target encryption method corresponding to the preset transaction type;

[0286] encrypting the target transaction data and / or the dynamic data in the target transaction data based on the target encryption method to obtain encrypted target transaction data, wherein the dynamic data in the encrypted target transaction data is in a locked state;

[0287] The encrypted target transaction data and the transaction signing method are transmitted to the application end, so that the application end displays the encrypted target transaction data based on the transaction signing method.

[0288] Optionally, when performing encryption processing on the target transaction data and / or dynamic data in the target transaction data based on the target encryption method, the processor 2001 specifically performs the following operations:

[0289] encrypting the dynamic data in the target transaction data based on a first encryption rule corresponding to a field identifier of the dynamic data; and / or

[0290] The target transaction data is encrypted based on a second encryption rule corresponding to the preset transaction type.

[0291] In an embodiment of the present specification, a target transaction data template is obtained through a transaction identifier, and target field parameters are obtained based on the field identifier of the dynamic field of the target transaction data template. The target field parameters are used to obtain dynamic data corresponding to the dynamic field, and target transaction data is generated based on the static data in the target transaction data template. The rendered target transaction data is transmitted to the application end for display, thereby generating target transaction data based on the computing resources of the server end through the target transaction data template. This can not only avoid transaction processing failures due to insufficient computing power on the application end, but also avoid data leakage during data transmission, thereby improving the efficiency, reliability and security of target transaction data generation. Furthermore, by performing data protection actions such as desensitization and encryption on dynamic data, the confidentiality of the generated target transaction data is improved, thereby avoiding data leakage during the transmission of the target transaction data to the application end, and improving the security and reliability of the application end receiving the target transaction data.

[0292] Those skilled in the art will appreciate that all or part of the processes in the above-described method embodiments can be implemented by instructing related hardware through a computer program. The program can be stored in a computer-readable storage medium, and when executed, the program can include the processes in the above-described method embodiments. The storage medium can be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

[0293] The above disclosure is only a preferred embodiment of this specification, and certainly cannot be used to limit the scope of rights of this specification. Therefore, equivalent changes made according to the claims of this specification are still within the scope covered by this specification.

Claims

1. A transaction processing method, applied to a server, comprising: Acquire template generation data corresponding to a preset transaction type, and acquire a transaction identifier and static data of the preset transaction type in the template generation data; Acquire dynamic fields and field identifiers in the template-generated data, and configure target field parameters corresponding to the dynamic fields, wherein the target field parameters include data acquisition rules and data protection rules; generating a target transaction data template corresponding to the preset transaction type based on the static data and the dynamic field, wherein the target transaction data template is used to generate target transaction data corresponding to the preset transaction type; The target transaction data template is stored based on the transaction identifier, and the dynamic field is stored based on the field identifier.

2. The method according to claim 1, wherein obtaining the dynamic fields and field identifiers in the template-generated data and configuring target field parameters corresponding to the dynamic fields comprises: Obtaining the dynamic fields in the template-generated data, as well as the field identifiers and field types corresponding to the dynamic fields; Determine a data source corresponding to the field type, and configure a data acquisition rule corresponding to the field identifier based on the data source, wherein the data acquisition rule indicates a method for acquiring dynamic data corresponding to the field identifier from the data source; Determining a sensitivity level corresponding to the field type based on the field type and the preset transaction type; If the sensitivity level indicates that the field type is a sensitive field, configuring a desensitization rule corresponding to the dynamic field based on the field type; Based on the field type and the preset transaction type, a first encryption rule corresponding to the field identifier is configured, where the first encryption rule is used to encrypt dynamic data corresponding to the dynamic field, and the encrypted dynamic data is in a locked state.

3. The method according to claim 1, wherein generating a target transaction data template corresponding to the preset transaction type comprises: A second encryption rule corresponding to the target transaction data template is configured based on the preset transaction type, where the second encryption rule is used to encrypt the target transaction data corresponding to the target transaction data template.

4. The method according to claim 1, wherein storing the target transaction data template based on the transaction identifier and storing the dynamic field based on the field identifier comprises: Storing the target transaction data template in a first database based on the transaction identifier; Based on the field identifier and the transaction identifier, the target field parameter of the dynamic field is stored in the second database and the local cache space of the server. The data reading priority of the local cache space is higher than that of the second database.

5. The method according to claim 4, wherein storing the target transaction data template in the first database based on the transaction identifier comprises: Based on the transaction identifier, the target transaction data template is stored in the first database of the server and in the cluster cache space corresponding to the server cluster to which the server belongs. The data reading priority of the cluster cache space is higher than that of the first database.

6. The method according to claim 5, wherein storing the target transaction data template in the first database of the server and in the cluster cache space corresponding to the server cluster to which the server belongs based on the transaction identifier comprises: Acquire a transaction signing mode corresponding to the transaction identifier in the template generation data, wherein the transaction signing mode indicates a display mode of target transaction data corresponding to the target transaction data template; Based on the transaction identifier, the transaction signing method and the target transaction data template are stored in the first database of the server and in the cluster cache space corresponding to the server cluster to which the server belongs.

7. The method according to claim 4, further comprising: If the historical transaction data template corresponding to the transaction identifier is stored in the cluster cache space corresponding to the server or the first database, the target transaction data template is updated to the historical transaction data template; If the local cache space or the second database stores historical field parameters corresponding to the field identifier, the historical field parameters are updated with the target field parameters.

8. A transaction processing method, applied to a server, comprising: If the server receives the transaction data generation request transmitted by the application, determining the transaction type in the transaction data generation request; If the transaction type is a preset transaction type, obtaining a target transaction data template corresponding to the preset transaction type, and obtaining a target field parameter corresponding to a dynamic field in the target transaction data template; Acquire dynamic data corresponding to the dynamic field based on the data acquisition rule and data protection rule corresponding to the target field parameter; generating target transaction data corresponding to the transaction data generation request based on the dynamic data and the static data in the target transaction data template; The target transaction data is transmitted to the application end so as to be displayed on the application end.

9. The method according to claim 8, wherein obtaining the target transaction data template corresponding to the preset transaction type and parsing and obtaining the target field parameters corresponding to the dynamic fields in the target transaction actual template comprises: Obtaining a transaction identifier of the preset transaction type, and obtaining a target transaction data template from a cluster cache space or a first database corresponding to the server based on the transaction identifier; Parsing the target transaction data template to obtain static data and dynamic fields in the target transaction data template; Based on the field identifier of the dynamic field, a target field parameter corresponding to the field identifier is acquired in the local cache space of the server or the second database.

10. The method according to claim 8, wherein acquiring the dynamic data corresponding to the dynamic field based on the data acquisition rule and the data protection rule in the target field parameter comprises: Determining a data acquisition interface corresponding to the dynamic field in the server based on a data acquisition rule corresponding to the target field parameter; Searching in the data source corresponding to the data acquisition interface to obtain the dynamic data corresponding to the dynamic field; If the dynamic field is a sensitive field, the dynamic data is desensitized based on the desensitization rules in the data protection rules to obtain the desensitized dynamic data, and the desensitized dynamic data is determined as the dynamic data corresponding to the dynamic field.

11. The method according to claim 8, wherein transmitting the target transaction data to the application end so as to display the target transaction data on the application end comprises: Acquire, based on the preset transaction type, a transaction signing method corresponding to the target transaction data and a target encryption method corresponding to the preset transaction type; encrypting the target transaction data and / or the dynamic data in the target transaction data based on the target encryption method to obtain encrypted target transaction data, wherein the dynamic data in the encrypted target transaction data is in a locked state; The encrypted target transaction data and the transaction signing method are transmitted to the application end, so that the application end displays the encrypted target transaction data based on the transaction signing method.

12. The method according to claim 11, wherein encrypting the target transaction data and / or dynamic data in the target transaction data based on the target encryption method comprises: encrypting the dynamic data in the target transaction data based on a first encryption rule corresponding to a field identifier of the dynamic data; and / or, The target transaction data is encrypted based on a second encryption rule corresponding to the preset transaction type.

13. A transaction processing device, comprising: a data acquisition unit, configured to acquire template generation data corresponding to a preset transaction type, and acquire a transaction identifier and static data of the preset transaction type in the template generation data; a configuration unit, configured to obtain dynamic fields and field identifiers in the template-generated data, and configure target field parameters corresponding to the dynamic fields, wherein the target field parameters include data acquisition rules and data protection rules; a template generating unit, configured to generate a target transaction data template corresponding to the preset transaction type based on the static data and the dynamic field, wherein the target transaction data template is used to generate target transaction data corresponding to the preset transaction type; A storage unit is configured to store the target transaction data template based on the transaction identifier and to store the dynamic field based on the field identifier.

14. A transaction processing device, comprising: a type determining unit, configured to determine a transaction type in a transaction data generation request if the server receives the transaction data generation request transmitted by the application; a template acquiring unit, configured to, if the transaction type is a preset transaction type, acquire a target transaction data template corresponding to the preset transaction type, and acquire a target field parameter corresponding to a dynamic field in the target transaction data template; a data acquisition unit, configured to acquire dynamic data corresponding to the dynamic field based on a data acquisition rule and a data protection rule corresponding to the target field parameter; a data generating unit, configured to generate target transaction data corresponding to the transaction data generation request based on the dynamic data and static data in the target transaction data template; A data transmission unit is used to transmit the target transaction data to the application end so as to display the target transaction data on the application end.

15. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer program code, and when the computer program code is executed, the method according to any one of claims 1 to 7 or 8 to 12 is implemented.

16. An electronic device comprising: A processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the steps of the method according to any one of claims 1 to 7 or 8 to 12.

17. A computer program product having at least one instruction stored thereon, wherein when the at least one instruction is executed by a processor, the steps of the method according to any one of claims 1 to 7 or 8 to 12 are implemented.

Images