A method and system for verifying electronic signatures of silver bullet contracts

Abstract

The application discloses a kind of silver enterprise contract electronic signature verification method and system, it is related to electronic signature technical field, including definition silver enterprise contract signature whole life cycle process, definition standard silver enterprise contract from formulation to the whole life cycle process of realization, provide reliable basis for the verification of subsequent electronic signature blockchain chain-up.In contract information and performance information extraction core information, and core information chain-up, ensure that blockchain can be associated to core information content, improve security and relevance.With the characteristics of signing link and performance link to carry out targeted risk assessment, determine risk situation.Combined with core information and risk degree to carry out blockchain chain-up on signing link and performance link respectively, improve the security and adaptability of signature, combined with acceptance information, signing link and performance link respective blockchain evidence signature generation acceptance link blockchain evidence signature, ensure the security of silver enterprise contract electronic signature verification.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of electronic signature, in particular to a bank-enterprise contract electronic signature verification method and system. BACKGROUND

[0002] The bank-enterprise contract electronic signature verification scheme relies on blockchain, digital certificate and public key infrastructure (PKI) technology to build a trust system covering the whole process of signing, performing and accepting. The scheme takes asymmetric encryption algorithm as the core, binds the enterprise identity through the CA agency issuing digital certificate to ensure the authenticity and non-repudiation of the signing party; uses hash function to generate a unique digest of the file, records the time sequence of each link combined with the timestamp service to form an unalterable evidence chain; and the blockchain distributed ledger technology realizes the cross-node synchronization and real-time verification of the stored data to ensure the complete association of data such as signing terms, performance logs and acceptance conclusions between links.

[0003] In the prior art, signature verification is often carried out after signing or acceptance, and the intermediate process cannot be verified, and the signature formed by the blockchain is not associated with the risk situation, resulting in poor accuracy and adaptability of the bank-enterprise contract electronic signature verification, and the safety of the whole process of the bank-enterprise contract cannot be guaranteed.

[0004] Therefore, how to improve the accuracy and adaptability of the bank-enterprise contract electronic signature verification is a technical problem to be solved at present. SUMMARY

[0005] The purpose of the present application is to solve the problem of poor accuracy and adaptability of the bank-enterprise contract electronic signature verification in the prior art, and a bank-enterprise contract electronic signature verification method is proposed, which comprises,

[0006] Defining the whole life cycle process of bank-enterprise contract signature, the whole life cycle process of bank-enterprise signature includes the link processes in the signing link, the performance link and the acceptance link in sequence;

[0007] Collecting contract information of the signing link and performance information of the performance link, extracting core information from the contract information and the performance information, and performing risk assessment on the contract information and the performance information to obtain the risk degree of the signing link and the performance link respectively;

[0008] Combining the core information and the risk degree to respectively chain the signing link and the performance link on the blockchain to generate the blockchain stored signature of the signing link and the performance link respectively;

[0009] Collecting acceptance information of the acceptance link, combining the acceptance information, the blockchain stored signature of the signing link and the performance link to generate the blockchain stored signature of the acceptance link, and verifying by means of the blockchain stored signature of the signing link, the performance link and the acceptance link respectively.

[0010] In some embodiments of this application, the full life cycle process of bank-enterprise contract signing is defined, including:

[0011] Determine the implementation processes of the contract signing, contract performance and acceptance stages respectively, set the split nodes in the implementation processes of the contract signing, contract performance and acceptance stages respectively, and confirm all basic signature information involved in the implementation processes of the contract signing, contract performance and acceptance stages respectively.

[0012] In some embodiments of the present application, core information is extracted from the contract information and performance information, including:

[0013] For the core information of the contract, NLP technology is used to extract all types of contract information from the bank-enterprise contract. The contract information categories are filtered according to the bank-enterprise contract type and business needs, and the filtered contract information is used as the core information of the contract;

[0014] For the core information on performance information, multiple contract standards are formulated through all categories of contract information, and the actual performance information is compared with multiple contract standards to generate performance deviation information. The performance deviation information is screened according to the bank-enterprise contract type and business needs, and the screened performance deviation information is used as the core information of the performance information.

[0015] In some embodiments of the present application, risk assessment of contract information and performance information includes:

[0016] Conduct risk assessment on contract information, break it down into multiple risk dimensions, quantify the risk of each risk dimension, and obtain the risk value of each risk dimension. Combine the risk values ​​of all risk dimensions to obtain the risk level of the contract signing process;

[0017] Integrate the contract events under the performance link, and arrange the performance process axis of the performance link according to the chronological order of the contract events. Mark the core information of the performance information at the corresponding position on the performance process axis, and conduct risk assessment of the performance information based on the basic signature information and core information of the performance link.

[0018] In some embodiments of the present application, risk assessment of performance information is performed based on the basic signature information and core information of the performance link, including:

[0019] The difficulty of performance monitoring is determined based on the basic signature information and the length of the performance process axis. Based on the difficulty of performance monitoring, multiple monitoring nodes are set on the performance process axis. The deviation value of the core information of each monitoring node is calculated based on the monitoring node. The risk level of the performance link is calculated by combining the deviation values ​​of the core information of all monitoring nodes.

[0020] In some embodiments of the present application, the contract signing process and the contract performance process are respectively put on the blockchain in combination with the core information and risk level, including:

[0021] Extract key content from core information and upload key content and risk levels to the blockchain during the contract signing process;

[0022] In the fulfillment phase, the deviation values ​​and key contents of the core information on each monitoring node are uploaded to the chain. After the fulfillment phase is completed, the risk level and key contents of the fulfillment phase are uploaded to the chain.

[0023] In some embodiments of the present application, the acceptance information of the acceptance phase is collected, including:

[0024] After the performance phase is completed, the contract objectives are determined in the bank-enterprise contract, the completion of the contract objectives is checked and accepted, and the completion of the contract objectives is used as the acceptance information of the acceptance phase.

[0025] In some embodiments of the present application, the blockchain evidence signature of the acceptance phase is generated by combining the acceptance information, the contract signing phase, and the performance phase, including:

[0026] The blockchain evidence signatures of the acceptance information, signing process and performance process are uploaded to the chain to generate the blockchain evidence signature of the acceptance process.

[0027] Correspondingly, this application also provides a bank-enterprise contract electronic signature verification system, including:

[0028] The first module is used to define the full life cycle process of bank-enterprise contract signing, which includes the signing phase, contract performance phase, and acceptance phase in three steps.

[0029] The second module is used to collect contract information from the contract signing phase and performance information from the performance phase, extract core information from the contract information and performance information, and conduct risk assessment on the contract information and performance information to obtain the risk level of each phase;

[0030] The third module is used to combine core information and risk levels to upload the contract signing and performance stages to the blockchain, generating blockchain signatures for each stage.

[0031] The fourth module is used to collect acceptance information of the acceptance link, combine the acceptance information, the blockchain evidence signatures of the signing link and the performance link to generate the blockchain evidence signature of the acceptance link, and verify it with the blockchain evidence signatures of the signing link, the performance link and the acceptance link.

[0032] Compared with the prior art, the present invention has the following beneficial effects:

[0033] 1. Define the full lifecycle process for bank-enterprise contract signing. Define the standard lifecycle process for bank-enterprise contracts, from formulation to implementation, to provide a reliable foundation for subsequent verification of electronic signatures on the blockchain. Extract core information from contract and fulfillment information and upload it to the blockchain to ensure that the blockchain can be linked to the core information content, improving security and relevance.

[0034] 2. Conduct risk assessments on contract and performance information, using the characteristics of the contract signing and performance phases to conduct targeted risk assessments and determine risk situations. Combine core information and risk levels to upload each phase of the contract signing and performance to the blockchain, improving the security and adaptability of signatures. Combine acceptance information, the blockchain-based signatures for the contract signing and performance phases to generate a blockchain-based signature for the acceptance phase, ensuring the security of electronic signature verification for bank-enterprise contracts. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 This is a flow chart of a method for verifying electronic signatures in bank-enterprise contracts proposed by the present invention;

[0036] Figure 2 This is a structural diagram of a bank-enterprise contract electronic signature verification system proposed by the present invention. DETAILED DESCRIPTION

[0037] The technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all the embodiments.

[0038] Reference Figure 1 A method for verifying an electronic signature of a bank-enterprise contract comprises the following steps:

[0039] Step S101, defining the full life cycle process of bank-enterprise contract signing, which includes the process steps in three orders: contract signing, contract performance and acceptance.

[0040] In this embodiment, the signing phase is the process of negotiation and consultation between Party A and Party B to jointly formulate a contract; the performance phase is the process of both parties performing business in accordance with the content of the contract; and the acceptance phase is the process of comprehensive acceptance of the business after the performance phase is completed. The three phases are implemented step by step in sequence.

[0041] In some embodiments of this application, the full life cycle process of bank-enterprise contract signing is defined, including:

[0042] Determine the implementation processes of the contract signing, contract performance and acceptance stages respectively, set the split nodes in the implementation processes of the contract signing, contract performance and acceptance stages respectively, and confirm all basic signature information involved in the implementation processes of the contract signing, contract performance and acceptance stages respectively.

[0043] In this embodiment, the basic signature information is the official seal of the corporate legal person or department manager, etc. The three links involve different contents, and the corresponding basic signature information is different. The split nodes are the starting and ending points of the contract signing link, performance link, and acceptance link, respectively, to mark the link boundaries or divide different links. The following is a partial example of the three-link process,

[0044] The signing process is as follows:

[0045] a. Identity verification (starting point): The enterprise obtains a digital certificate from a CA organization, and the bank verifies the binding relationship between the enterprise's business license, legal person ID card and other physical documents and the digital certificate.

[0046] b. Contract drafting: The bank system generates a standardized contract template, and the enterprise uploads supplementary terms (such as loan purpose and guarantee method) through the electronic signature platform.

[0047] c. Terms Negotiation: The two parties compare the terms through the blockchain smart contract, automatically mark the differences (such as interest rate fluctuation range, repayment period), and generate revision records.

[0048] d. Electronic Signature (End Point): The corporate legal person uses UKey or mobile shield to complete the contract signing, and the bank system automatically affixes the timestamp and bank electronic official seal.

[0049] Implementation process of the fulfillment phase

[0050] a. Contract execution (starting point): The bank disburses the loan as agreed in the contract, and the enterprise uses the funds as planned (e.g., transferring the loan to a supplier's account through entrusted payment).

[0051] b. Performance monitoring: Banks monitor the use of funds through IoT devices (such as GPS positioning of financed vehicles) and ERP system integration (real-time access to corporate inventory data).

[0052] c. Deviation handling: If the enterprise fails to repay the loan as agreed (e.g., overdue for more than 3 days), the smart contract will automatically trigger an early warning, generate a "Performance Deviation Notice" and send it to the accounts of both parties.

[0053] d. Signature and seal update: After the enterprise pays the outstanding debt, the bank will stamp the "Performance Confirmation Stamp" in the system and update the performance status to "normal".

[0054] e. Satisfaction of contract termination conditions (end point): The termination conditions are determined according to the contract content. Even if the contract objectives are not achieved, the contract can be terminated. For example, multiple violations, timeout exceeding the threshold, etc.

[0055] Acceptance process implementation process

[0056] a. Target Verification: The bank compares the contract target (e.g., "project commissioning rate ≥ 80%)" with the actual completion status (e.g., the "Project Completion Acceptance Report" submitted by the enterprise), or uses a third-party testing agency to verify the project completion status or quality.

[0057] b. Document review: The enterprise uploads supporting documents such as invoices and logistics documents. The bank uses OCR technology to extract key data (such as amount and date) and cross-verify it with the contract terms.

[0058] c. Signature generation: After acceptance, the bank system automatically generates an "Acceptance Certificate" and stamps it with the bank's electronic official seal and the company's electronic signature.

[0059] d. Archiving: Package the evidence data of acceptance signatures, contract signing, and contract performance, and upload them to the judicial blockchain node (such as the Beijing Internet Court Tianping Chain).

[0060] It is understandable that the above three steps are only partial examples and do not represent all the steps for implementing the process. They can be adjusted or changed according to actual conditions.

[0061] Step S102, collect the contract information of the contract signing stage and the performance information of the performance stage, extract the core information from the contract information and the performance information, and conduct risk assessment on the contract information and the performance information to obtain the risk level of each of the contract signing stage and the performance stage respectively.

[0062] In this embodiment, the contract information in the signing process includes contract-related information (basic contract information, clause information, basic signature information, etc.).

[0063] 1. Basic contract information

[0064] Core content:

[0065] Contract number, contract name, contract type (such as loan contract, guarantee contract)

[0066] Information of the contracting parties (company name, unified social credit code, bank name, branch code)

[0067] Contract amount, currency, term (start and end dates), interest rate (fixed / floating)

[0068] Funding purpose (such as purchasing raw materials, equipment upgrades), repayment method (equal installments of principal and interest / repayment of principal at maturity)

[0069] Collection method:

[0070] Enterprises fill out standardized forms through the bank's electronic signature platform, and the system automatically verifies the integrity of the fields (for example, the amount must be consistent with the bank's credit approval result).

[0071] Banks synchronize approved contract parameters (such as interest rates and terms) from core business systems to avoid manual entry errors.

[0072] 2. Terms and Conditions

[0073] Core content:

[0074] Key terms: liability for breach of contract (such as overdue penalty interest rate), early repayment conditions, and security method (mortgage / pledge / guarantee)

[0075] Attachments: Supplementary agreements (such as interest rate adjustment mechanism), collateral list (mortgage property address, assessed value)

[0076] Special terms: regulatory account requirements (e.g. loan funds need to be transferred to a designated supplier account)

[0077] Collection method:

[0078] Use structured templates: The bank provides a library of preset terms (such as "overdue penalty interest = unpaid principal × daily interest rate × 1.5 times"), and the enterprise selects or modifies the parameters.

[0079] 3. Basic signature information

[0080] Core content:

[0081] Enterprise side: Digital certificate fingerprint of legal person seal and contract seal (used to verify the authenticity of the signature)

[0082] Bank side: electronic seal serial number of contract seal and business official seal

[0083] Signature timestamp (accurate to the second), signature location (contract page number)

[0084] Collection method:

[0085] The electronic signature system automatically records: the signature metadata (such as certificate fingerprint and timestamp) is written into the contract XML file through the API interface.

[0086] Third-party evidence storage: synchronized to the judicial blockchain (such as the Beijing Internet Court Tianping Chain) to generate a unique evidence storage number.

[0087] The performance information of the performance link includes the performance of each party's obligations, and then each party extracts the core information required for its own link (fund performance information, business performance information, change information, etc.).

[0088] 1. Fund fulfillment information

[0089] Core content:

[0090] Loan disbursement: disbursement amount, disbursement time, and receiving account (corporate account / supplier account)

[0091] Repayment record: repayment amount for each period, repayment time, repayment method (active deduction / manual transfer)

[0092] Fund usage: loan fund flow (e.g., transfer to Company A's account through entrusted payment for equipment purchase)

[0093] Collection method:

[0094] The bank's core system automatically records: the transaction serial number is associated with the contract number to generate a "Loan Disbursement / Repayment Details Table".

[0095] IoT monitoring: Install GPS devices on collateral (such as financed vehicles) and upload location data to the bank's risk control platform in real time.

[0096] 2. Business performance information

[0097] Core content:

[0098] Project progress: For engineering contracts, a "Project Progress Report" (completed work volume, next steps) is required.

[0099] Goods delivery: If the purchase contract requires the collection of the Goods Receipt (signatory, receipt time, quantity of goods)

[0100] Service provision: If a consulting contract requires the collection of a "Service Acceptance Form" (service content, acceptance results)

[0101] Collection method:

[0102] Enterprise upload attachments: Upload the performance certification materials in PDF / image format through the bank's corporate online banking or API interface.

[0103] AI review: OCR identifies key fields in the receipt (such as the signatory's name) and automatically matches them with the reserved contract information.

[0104] 3. Change information

[0105] Core content:

[0106] Contract change records (such as extension applications, interest rate adjustments)

[0107] Supplementary agreement signing information (such as the changed repayment schedule)

[0108] Collection method:

[0109] Version control: A new contract version is generated for each change, and historical versions and change notes are retained.

[0110] Electronic signature re-signing: Re-sign the changed terms and associate them with the original contract number.

[0111] In some embodiments of the present application, core information is extracted from the contract information and performance information, including:

[0112] For the core information of the contract, NLP technology is used to extract all types of contract information from the bank-enterprise contract. The contract information categories are filtered according to the bank-enterprise contract type and business needs, and the filtered contract information is used as the core information of the contract;

[0113] For the core information on performance information, multiple contract standards are formulated through all categories of contract information, and the actual performance information is compared with multiple contract standards to generate performance deviation information. The performance deviation information is screened according to the bank-enterprise contract type and business needs, and the screened performance deviation information is used as the core information of the performance information.

[0114] In this embodiment, NLP technology enables comprehensive contract information extraction. The technical framework includes: Pre-trained models: Using Chinese pre-trained models such as BERT and RoBERTa, adapted for financial terminology (e.g., "extension" and "trustee payment"). Named Entity Recognition (NER): Training a custom NER model to identify key entities in the contract (e.g., contract number, interest rate, collateral). Relationship extraction: Dependency parsing extracts logical relationships between clauses (e.g., the calculation relationship in "Late payment penalty = outstanding principal × daily interest rate × 1.5 times").

[0115] Based on the contract type and business requirements, the filtering rule engine is as follows:

[0116] Contract type dimension:

[0117] Loan contract: retention amount, term, interest rate, repayment method, and guarantee method;

[0118] Guarantee contract: retain collateral information, appraisal value, and mortgage rate;

[0119] Factoring contract: retains the amount of accounts receivable, buyer information, and repurchase terms.

[0120] Business demand dimension:

[0121] Risk control department: Prioritize the extraction of default clauses and guarantee coverage ratio;

[0122] Finance department: focus on interest rate type (fixed / floating) and repayment schedule;

[0123] Regulatory compliance: purpose of withdrawn funds and proportion of entrusted payments.

[0124] For core performance information, NLP extracts original contract information (such as contract terms, annexes, and supplementary agreements). Clauses are categorized based on business attributes, with clauses divided into numerical categories (such as amount, interest rate, and term), logical categories (such as fund use and guarantee conditions), and time categories (such as repayment date and grace period). Rules are extracted. Explicit rules directly extract quantitative clauses (such as "interest rate = LPR + 100BP"). Implicit rules derive constraints through semantic analysis (such as "loan funds must be used to purchase raw materials," which implies "fund flow must match the procurement contract"). This allows for the development of multiple contract standards.

[0125] Actual performance information is collected from, but not limited to, internal bank systems: core systems (transaction records), credit systems (repayment records), and online banking systems (fund transfer receipts); enterprise-side data: external evidence such as purchase contracts and receipts obtained through direct bank-enterprise connections or the enterprise ERP system; and third-party data: credit reports, industrial and commercial information, and court enforcement information (for collateral status verification). Standardized formats are implemented (e.g., dates are standardized to YYYY-MM-DD); missing values ​​are handled (e.g., default values ​​are used to fill in unprovided repayment plans); and outlier detection is performed (e.g., triggering manual review when a single transaction exceeds 10 times the contract limit). Item-by-item standard verification: actual values ​​are compared against standard values ​​for each contract standard; logical relationship verification: dependencies between multiple standards are checked (e.g., "collateral seizure" triggers "loan early maturity" clauses). A structured deviation report is generated, including the deviation ID, contract number, standard requirements, actual performance, related clauses, and supporting evidence (e.g., transaction flow screenshots).

[0126] Different types of bank-enterprise contracts and different business needs have different focuses on performance deviations, so deviation information is screened.

[0127] In some embodiments of the present application, risk assessment of contract information and performance information includes:

[0128] Conduct risk assessment on contract information, break it down into multiple risk dimensions, quantify the risk of each risk dimension, and obtain the risk value of each risk dimension. Combine the risk values ​​of all risk dimensions to obtain the risk level of the contract signing process;

[0129] Integrate the contract events under the performance link, and arrange the performance process axis of the performance link according to the chronological order of the contract events. Mark the core information of the performance information at the corresponding position on the performance process axis, and conduct risk assessment of the performance information based on the basic signature information and core information of the performance link.

[0130] In this embodiment, contract terms are broken down into quantifiable risk factors, covering four major categories of risk: credit, market, operational, and compliance. Contracts are static, legally binding, so contract risk is assessed from these perspectives. The credit risk of the principal is the borrower / guarantor's probability of default (e.g., credit rating, historical overdue records). The transaction structure (market) risk is the rationality of the contract terms (e.g., interest rate pricing, repayment method, and guarantee coverage ratio). Compliance risk is whether the contract complies with regulatory requirements (e.g., interest rate cap, capital ratio, and restrictions on related-party transactions). Operational risk is the process loopholes in contract signing and contract performance management (e.g., signature authenticity, system integration stability). Risk quantification models can include: expert scoring: risk control experts assign scores from 1 to 10 for difficult-to-quantify dimensions (e.g., compliance risk); statistical modeling: using algorithms such as logistic regression and XGBoost to predict default probability for quantifiable dimensions (e.g., credit risk); and rule-based engine approaches: using rules to directly determine the risk level for hard indicators (e.g., whether the interest rate exceeds the regulatory cap).

[0131] Sort out the contract events that are stipulated or not stipulated in the contract, sort them in chronological order, build the fulfillment process axis, and set the monitoring nodes considering the length of the fulfillment process axis and the basic signature situation.

[0132] In some embodiments of the present application, risk assessment of performance information is performed based on the basic signature information and core information of the performance link, including:

[0133] The difficulty of performance monitoring is determined based on the basic signature information and the length of the performance process axis. Based on the difficulty of performance monitoring, multiple monitoring nodes are set on the performance process axis. The deviation value of the core information of each monitoring node is calculated based on the monitoring node. The risk level of the performance link is calculated by combining the deviation values ​​of the core information of all monitoring nodes.

[0134] In this embodiment, the difficulty of performance monitoring is determined based on the basic signature information and the length of the performance process axis. The signature difficulty is determined by considering the basic signature type, quantity and other information. The process difficulty is determined by considering the length of the performance process axis (duration, i.e., axis length, and the number of contract events). The performance monitoring difficulty is determined based on the signature difficulty and the process difficulty. The higher the performance monitoring difficulty, the more monitoring nodes are set. This monitoring node can be a time node or other node that can be accurately quantified during the performance process, which is used to monitor the safety situation during the performance process.

[0135] The calculation formula for the risk level of the performance phase is as follows: Among them, the deviation value of the core information of each monitoring node is the deviation degree obtained by integrating all the core information (implementation deviation information) under the monitoring node. The deviation degree indirectly reflects the risk situation. is the risk level of the performance phase (overall risk), is the number of monitoring nodes in the fulfillment phase, For the The risk weight corresponding to each monitoring node (determined by the location of the node, that is, the contract events near the monitoring node), For the The deviation value of the core information corresponding to each monitoring node, They are The maximum and minimum values ​​in is a preset constant, Represents the average value determined by the two extreme values ​​to the class average value ( , slightly larger than the general average), the constant is used to balance the size of the correction function.

[0136] In step S103, the contract signing process and the contract performance process are respectively put on the blockchain in combination with the core information and the risk level, and blockchain evidence signatures for the contract signing process and the contract performance process are generated.

[0137] In some embodiments of the present application, the contract signing process and the contract performance process are respectively put on the blockchain in combination with the core information and risk level, including:

[0138] Extract key content from core information and upload key content and risk levels to the blockchain during the contract signing process;

[0139] In the fulfillment phase, the deviation values ​​and key contents of the core information on each monitoring node are uploaded to the chain. After the fulfillment phase is completed, the risk level and key contents of the fulfillment phase are uploaded to the chain.

[0140] In this embodiment, during the contract signing phase, natural language processing techniques (such as keyword extraction algorithms and text summarization algorithms) are used to extract key content from the collected core contract-related information. For example, if the core information is a contract text, key information such as the contracting parties (Party A and Party B), the subject matter (such as the product name and service content), the contract amount, and the contract term are extracted. The extracted key content is organized and stored according to a predetermined data structure for subsequent blockchain upload. A blockchain platform is identified, and an appropriate blockchain network (such as a public, consortium, or private blockchain) is selected. Nodes are deployed and configured according to the platform's requirements. The organized key content from the contract signing phase and the assessed risk level are packaged according to the transaction format specified by the blockchain platform. For example, the key content is organized in JSON format, and the risk level is added as a field to form a complete transaction data packet. Using the SDK (Software Development Kit) or API (Application Programming Interface) provided by the blockchain platform, the packaged transaction data packet is sent to the blockchain network for blockchain upload by calling the corresponding transaction sending interface. The nodes in the blockchain network will verify and reach consensus on the transaction. Once consensus is reached, the transaction will be recorded in the blockchain block, completing the uploading of key content and risk levels of the signing process.

[0141] Before the contract fulfillment phase begins, multiple monitoring nodes should be set up based on the specific contract content and fulfillment process. For example, for a construction project contract, monitoring nodes might be set up for completion of foundation construction, topping out of the main structure, and completion of renovations. Blockchain platform selection: Based on business needs, data security, and privacy requirements, select an appropriate blockchain platform, such as Ethereum or Hyperledger Fabric. Network deployment and configuration: Complete the deployment of the blockchain network, including node setup, network topology configuration, and consensus mechanism configuration. Ensure the blockchain network operates properly and meets the business's performance and security requirements.

[0142] Monitoring nodes on the chain:

[0143] Data Encapsulation: For each monitoring node, the compiled key information and calculated deviation values ​​are encapsulated according to the transaction format specified by the blockchain platform. For example, on the Ethereum platform, smart contracts can be used to define the transaction data structure, with the key information and deviation values ​​used as input parameters of the smart contract.

[0144] Transaction sending: The encapsulated transaction data is sent to the blockchain network through the SDK (Software Development Kit) or API (Application Programming Interface) provided by the blockchain platform. Necessary signature information is required when sending a transaction to ensure the legitimacy and security of the transaction.

[0145] Node Verification and Consensus: After receiving a transaction, a node in the blockchain network first verifies it, checking for correct formatting, valid signatures, and sufficient permissions on the sender. Once verified, the transaction is placed in a pending transaction pool. Nodes then reach agreement on the order and validity of transactions through a consensus mechanism (such as proof-of-work or proof-of-stake). Once consensus is reached, the transaction is recorded in the latest block of the blockchain.

[0146] Generate Node Certificate: After a transaction is successfully uploaded to the blockchain, the blockchain platform will generate a blockchain certificate for the monitoring node based on the transaction's hash value and other information. This certificate includes key content, deviation values, and the transaction's location on the blockchain, serving as proof of the monitoring node's performance.

[0147] The fulfillment phase is completed and uploaded to the chain

[0148] Data packaging: The risk level and key details of the fulfillment phase are packaged according to the transaction format of the blockchain platform. Similarly, smart contracts or other data structures can be used to organize this information.

[0149] Transaction sending and verification: Through the blockchain platform's SDK or API, the packaged transaction is sent to the blockchain network. Nodes in the network will verify the transaction to ensure the integrity and legitimacy of the data.

[0150] Consensus and on-chain: Verified transactions enter the consensus process, where nodes use a consensus algorithm to reach agreement on the order and validity of transactions. Once consensus is reached, the transaction is recorded in the latest block of the blockchain, completing the on-chain assessment of the risks and key details of the fulfillment process.

[0151] Generate a proof of contract: After a transaction is successfully uploaded to the blockchain, the blockchain platform generates a proof of contract. This proof includes key details about the contract, the risk level, and the transaction's location on the blockchain, allowing for auditing and verification of the entire contract process.

[0152] Step S104: collect the acceptance information of the acceptance link, combine the acceptance information, the blockchain evidence signatures of the contract signing link and the performance link to generate the blockchain evidence signature of the acceptance link, and verify it with the blockchain evidence signatures of the contract signing link, the performance link and the acceptance link.

[0153] In some embodiments of the present application, the acceptance information of the acceptance phase is collected, including:

[0154] After the performance phase is completed, the contract objectives are determined in the bank-enterprise contract, the completion of the contract objectives is checked and accepted, and the completion of the contract objectives is used as the acceptance information of the acceptance phase.

[0155] In some embodiments of the present application, the blockchain evidence signature of the acceptance phase is generated by combining the acceptance information, the contract signing phase, and the performance phase, including:

[0156] The blockchain evidence signatures of the acceptance information, signing process and performance process are uploaded to the chain to generate the blockchain evidence signature of the acceptance process.

[0157] In this embodiment, after the contract fulfillment phase is completed, the contract objectives are carefully reviewed and clarified based on the specific terms and provisions of the bank-enterprise contract. Contract objectives may include, but are not limited to, specific business indicators, such as achieving a certain level of financial product transaction volume or a specific standard for on-time corporate loan repayments; or service delivery standards, such as achieving an agreed-upon professional level in financial advisory services or ensuring that the stability of the financial system meets a specified uptime.

[0158] Collect actual data and information related to contract objectives. For business indicator objectives, obtain data such as actual transaction volume and repayment records through financial transaction systems and corporate financial systems. For service delivery standard objectives, collect relevant information through customer feedback, system monitoring reports, and third-party evaluations.

[0159] Compare and analyze the collected actual data with the contract targets to determine the completion of the contract targets. For example, for a trading volume target, calculate the ratio of actual trading volume to target trading volume; for a system stability target, calculate the degree to which the actual system uptime meets the agreed uptime.

[0160] Record the completion status of the contract objectives in a structured form as acceptance information for the acceptance phase.

[0161] Integrate the acceptance information, contract signing, and contract performance blockchain evidence signatures. Data concatenation, association mapping, and other methods can be used to organically combine the three elements into a complete data set. For example, acceptance information can be added as a new field to the data structure of the contract signing and contract performance evidence signatures, or a relationship table can be established to record the correspondence between acceptance information and the contract signing and contract performance evidence signatures. Select an appropriate blockchain platform and node for on-chain processing. Based on business needs and security requirements, you can choose the same blockchain network used for the contract signing and contract performance phases, or a blockchain network dedicated to the acceptance phase. Encapsulate the integrated data according to the blockchain platform's transaction format. For example, on the Ethereum platform, you can write a smart contract to define the data structure of the acceptance evidence signature and use the integrated data as input parameters for the smart contract. Use the blockchain platform's SDK or API to send the encapsulated transaction data to the blockchain network for on-chain processing. Nodes in the network will verify and reach consensus on the transaction. Once consensus is reached, the transaction is recorded in a blockchain block, generating a blockchain evidence signature for the acceptance phase.

[0162] The signatures and seals recorded during the contract signing process record the contract's initial core terms and agreements. The signatures and seals recorded during the contract performance phase reflect the actual progress and deviations during contract execution. The signatures and seals recorded during the acceptance phase demonstrate whether the final results meet the requirements. These three mutually reinforce each other, forming a complete information chain and making the acceptance results more credible. For example, in large-scale engineering projects, project quality standards are clearly defined at the time of contract signing, and construction status and quality inspection data at each stage are recorded during the contract performance process. During acceptance, a comprehensive project assessment is conducted based on this preliminary information, ensuring that all parties can be confident that the acceptance results are based on authentic and comprehensive data.

[0163] By integrating information from the contract signing, contract fulfillment, and acceptance phases to generate a signature for the acceptance phase, the integrity of the entire business process is ensured. From contract signing to execution and final acceptance, information from each key step is recorded on the blockchain, forming a complete business archive. For example, in a software procurement project, the contract signing phase records the software's functional requirements and delivery time, the contract fulfillment phase records the software's development progress and testing, and the acceptance phase conducts a comprehensive inspection of the software based on this preliminary information. The inspection results are then stored along with the previous information, ensuring the integrity of the entire project process.

[0164] In traditional business processes, information is often scattered across different departments or systems, making it prone to loss or omission. Blockchain technology, however, centrally stores information from various stages and links them through evidence and signatures, effectively preventing information loss. For example, in supply chain finance, the contract signing process records purchase contract information, the fulfillment process records transportation and warehousing information, and the acceptance process records quality inspection information. Blockchain evidence and signatures integrate this information, ensuring the integrity and accuracy of supply chain finance operations.

[0165] The blockchain-based evidence signatures at each stage contain unique identification information such as timestamps and transaction hashes, providing clear traceability throughout the entire business process. If problems are discovered during the acceptance phase, the evidence signatures can be used to quickly locate relevant information from the contract signing and performance stages, identifying the root cause of the problem.

[0166] Correspondingly, this application also provides a bank-enterprise contract electronic signature verification system, such as Figure 2 Shown, including,

[0167] The first module is used to define the full life cycle process of bank-enterprise contract signing, which includes the signing phase, contract performance phase, and acceptance phase in three steps.

[0168] The second module is used to collect contract information from the contract signing phase and performance information from the performance phase, extract core information from the contract information and performance information, and conduct risk assessment on the contract information and performance information to obtain the risk level of each phase;

[0169] The third module is used to combine core information and risk levels to upload the contract signing and performance stages to the blockchain, generating blockchain signatures for each stage.

[0170] The fourth module is used to collect acceptance information of the acceptance link, combine the acceptance information, the blockchain evidence signatures of the signing link and the performance link to generate the blockchain evidence signature of the acceptance link, and verify it with the blockchain evidence signatures of the signing link, the performance link and the acceptance link.

[0171] Compared with the prior art, the present invention has the following beneficial effects:

[0172] 1. Define the full lifecycle process for bank-enterprise contract signing. Define the standard lifecycle process for bank-enterprise contracts, from formulation to implementation, to provide a reliable foundation for subsequent verification of electronic signatures on the blockchain. Extract core information from contract and fulfillment information and upload it to the blockchain to ensure that the blockchain can be linked to the core information content, improving security and relevance.

[0173] 2. Conduct risk assessments on contract and performance information, using the characteristics of the contract signing and performance phases to conduct targeted risk assessments and determine risk situations. Combine core information and risk levels to upload each phase of the contract signing and performance to the blockchain, improving the security and adaptability of signatures. Combine acceptance information, the blockchain-based signatures for the contract signing and performance phases to generate a blockchain-based signature for the acceptance phase, ensuring the security of electronic signature verification for bank-enterprise contracts.

[0174] Through the above description of the embodiments, those skilled in the art will clearly understand that the present invention can be implemented via hardware or via software combined with a necessary general-purpose hardware platform. Based on this understanding, the technical solution of the present invention can be embodied in the form of a software product. This software product can be stored on a non-volatile storage medium (such as a CD-ROM, USB flash drive, or external hard drive) and includes instructions for enabling a computer device (such as a personal computer, server, or network device) to execute the methods described in various implementation scenarios of the present invention.

[0175] Those skilled in the art will understand that the accompanying drawings are merely schematic diagrams of a preferred implementation scenario, and the modules or processes in the accompanying drawings are not necessarily required to implement the present invention.

[0176] Those skilled in the art will appreciate that the modules in the system of the implementation scenario can be distributed in the system of the implementation scenario according to the implementation scenario description, or can be modified accordingly and located in one or more systems different from the implementation scenario. The modules of the above implementation scenario can be combined into one module or further divided into multiple submodules.

[0177] The above description is only a preferred specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any technician familiar with the technical field, within the technical scope disclosed by the present invention, who makes equivalent replacements or changes based on the technical solution and inventive concept of the present invention, should be covered by the scope of protection of the present invention.

Claims

1. A method for verifying electronic signatures of bank-enterprise contracts, characterized in that: include, Define the full life cycle process of bank-enterprise contract signing, which includes the signing phase, contract performance phase, and acceptance phase in three steps; Collect contract information from the contract signing phase and performance information from the performance phase, extract core information from the contract information and performance information, and conduct risk assessment on the contract information and performance information to obtain the risk level of each phase; Combine core information and risk levels to upload the contract signing and performance stages to the blockchain, generating blockchain signatures for each stage. Collect the acceptance information of the acceptance phase, combine the acceptance information, the blockchain evidence signatures of the contract signing phase and the contract performance phase to generate the blockchain evidence signature of the acceptance phase, and verify it with the blockchain evidence signatures of the contract signing phase, the contract performance phase and the acceptance phase; in, For the core information on performance information, multiple contract standards are developed based on all types of contract information. These standards are used to compare actual performance information to generate performance deviation information. Performance deviation information is filtered based on the bank-enterprise contract type and business needs, and the filtered performance deviation information is used as the core information of performance information. Integrate the contract events under the performance phase, and arrange the performance process axis of the performance phase according to the chronological order of the contract events. Mark the core information of the performance information at the corresponding position on the performance process axis, and conduct risk assessment of the performance information based on the basic signature information and core information of the performance phase; Conduct risk assessment of performance information based on the basic signature information and core information of the performance link, including: The difficulty of performance monitoring is determined based on the basic signature information and the length of the performance process axis. Based on the difficulty of performance monitoring, multiple monitoring nodes are set on the performance process axis. The deviation value of the core information of each monitoring node is calculated based on the monitoring node. The risk level of the performance link is calculated by combining the deviation values ​​of the core information of all monitoring nodes.

2. The bank-enterprise contract electronic signature verification method according to claim 1, characterized in that: Define the full life cycle process of bank-enterprise contract signing, include, Determine the implementation processes of the contract signing, contract performance and acceptance stages respectively, set the split nodes in the implementation processes of the contract signing, contract performance and acceptance stages respectively, and confirm all basic signature information involved in the implementation processes of the contract signing, contract performance and acceptance stages respectively.

3. The bank-enterprise contract electronic signature verification method according to claim 1, characterized in that: Extract core information from contract information and performance information, including: For the core information of the contract, all categories of contract information are extracted from the bank-enterprise contract through NLP technology, and the categories of contract information are filtered according to the bank-enterprise contract type and business needs, and the filtered contract information is used as the core information of the contract.

4. The bank-enterprise contract electronic signature verification method according to claim 3, characterized in that: Conduct risk assessments on contract information and performance information, including: Conduct risk assessment on contract information, break down contract information into multiple risk dimensions, quantify the risk of each risk dimension, obtain the risk value of each risk dimension, and combine the risk values ​​of all risk dimensions to obtain the risk level of the contract signing process.

5. The bank-enterprise contract electronic signature verification method according to claim 1, characterized in that: Combine core information and risk levels to put the contract signing and performance stages on the blockchain, including: Extract key content from core information and upload key content and risk levels to the blockchain during the contract signing process; In the fulfillment phase, the deviation values ​​and key contents of the core information on each monitoring node are uploaded to the chain. After the fulfillment phase is completed, the risk level and key contents of the fulfillment phase are uploaded to the chain.

6. The bank-enterprise contract electronic signature verification method according to claim 1, characterized in that: Collect acceptance information for the acceptance phase, including: After the performance phase is completed, the contract objectives are determined in the bank-enterprise contract, the completion of the contract objectives is checked and accepted, and the completion of the contract objectives is used as the acceptance information of the acceptance phase.

7. The bank-enterprise contract electronic signature verification method according to claim 1, characterized in that: Combine the blockchain evidence signatures of the acceptance link, the signing link, and the performance link to generate the blockchain evidence signature of the acceptance link, including: The blockchain evidence signatures of the acceptance information, signing process and performance process are uploaded to the chain to generate the blockchain evidence signature of the acceptance process.

8. A bank-enterprise contract electronic signature verification system, characterized by: For implementing the bank-enterprise contract electronic signature verification method according to any one of claims 1 to 7, the system comprises: The first module is used to define the full life cycle process of bank-enterprise contract signing, which includes the signing phase, contract performance phase, and acceptance phase in three steps. The second module is used to collect contract information from the contract signing phase and performance information from the performance phase, extract core information from the contract information and performance information, and conduct risk assessment on the contract information and performance information to obtain the risk level of each phase; The third module is used to combine core information and risk levels to upload the contract signing and performance stages to the blockchain, generating blockchain signatures for each stage. The fourth module is used to collect acceptance information of the acceptance link, combine the acceptance information, the blockchain evidence signatures of the signing link and the performance link to generate the blockchain evidence signature of the acceptance link, and verify it with the blockchain evidence signatures of the signing link, the performance link and the acceptance link.

Images