Electronic signature service method and system compatible with multiple CA certificates

Abstract

The invention provides an electronic signature service method and system compatible with multiple CA certificates, independent and unified standard functions, interfaces and processes such as certificates, seals, configuration rules and dragged seal signing are formed in a platform system, and API interfaces such as PDF seal picture synthesis and keyword search are carried out by utilizing a JAVA component and an itext component. A virtual complete signing process can be completed before no task is accessed to a CA service provider, and a previewed PDF file is formed; and according to subsequent docking of different CA digital certificates, APIs of different CA digital certificate service providers are accessed to complete configuration, rule explanation, signature authorization verification and the like in links of certificate management, seal management, rule configuration, seal dragging signature and the like, such as signature of seal positions of all parties, automatic signature and the like. According to the invention, various CA digital certificates and different API services and personalized requirements of providers can be flexibly corresponded, and various signing scenes and process specifications of existing users can be met to the greatest extent.

Description

Technical Field

[0001] The present invention relates to the technical field of electronic signature services, and in particular to an electronic signature service method and system compatible with multiple CA certificates. Background Art

[0002] There are already many CA digital certificate service providers on the market. Faced with different e-commerce trading platforms and business needs, enterprises and individual users often have registered and possess CA certificates. However, most current Internet trading platform systems often only provide signing methods for a specific CA digital certificate. If the CA certificate service provider currently held by the user is not the same, he or she often has to apply for another CA digital certificate, resulting in a waste of signing costs and time.

[0003] Patent application document CN109831308A discloses a digital signature authentication method, storage medium and device, which includes: a credential acquisition step, in response to a digital signature request initiated by an enterprise user, sending contract information to a CA institution, and obtaining a digital signature credential from the CA institution; a document signing step, according to the digital signature credential, sending an electronic document to a CA institution for digital signature, and receiving a digitally signed electronic document from the CA institution. However, this patent cannot completely solve the existing technical problems, nor can it meet the needs of the present invention. Summary of the invention

[0004] In view of the defects in the prior art, the object of the present invention is to provide an electronic signature service method and system compatible with multiple CA certificates.

[0005] The electronic signature service method compatible with multiple CA certificates provided by the present invention includes:

[0006] Step S1: Create a certificate management module to implement certificate application, deletion, modification and viewing functions, and add application verification, payment and interactive callback functions;

[0007] Step S2: Create a seal management module to implement the functions of adding, deleting, modifying, viewing and verifying user seals;

[0008] Step S3: Create a signing rule configuration module, predefine the number of signatories and signing methods for different types of signing services, and set the seal type, seal number, and seal page position;

[0009] Step S4: Create a unified signing operation interface. Before calling the certificate to sign the document, all normative operations are regulated by preset rules. When signing, the application function API of different CA service providers is called according to the CA digital certificate selected by the user, or the signing request is sent to the interface to complete the actual signing;

[0010] Step S5: Create a signing interaction docking module to achieve functional docking between the local application function API and the application function API of each CA service provider.

[0011] Preferably, step S1 includes: collecting CA service provider mark, company name, legal person name and application document through common field information, and realizing personalized information collection according to selecting different CA digital certificates; in the process of verification, payment and interactive callback, realizing it by calling different API interfaces and processing procedures according to different CA service providers; embedding a platform operation function for verifying the unified application information in the certificate application submission link;

[0012] The step S2 includes: uploading a set of seals to different CA service providers' signing systems; binding the effective certificate list with the platform certificate record, and saving the seal IDs returned by each CA service provider; presetting the seal for initializing the signature or configuring the real seal when signing automatically.

[0013] Preferably, step S3 includes: defining the number of signatories as unilateral, bilateral or multi-party, and defining the signing order; setting a certain signatory to sign automatically or manually, and automatic signing requires signing an authorization letter and setting the CA digital certificate selected for automatic signing; specifying the type, quantity and position of the seal, and controlling whether manual dragging or not is allowed for the seal position; defining the filling in of the cover information of the predetermined document before signing the contract and automatically generating merge rules.

[0014] Preferably, step S4 includes: the operations of the unified signing interface are signed in sequence according to the signing order, and the signing initiator is the first signer by default; all CA digital certificates are selected when the first party signs, or the signing initiator sets the CA digital certificate service provider by default or forcibly specifies it; the unified signing interface accesses the personalized requirements of the CA service provider according to user needs and security requirements; the JAVA version of itext component is used to realize the signing document and seal and dynamic page generation and merging, PDF parsing image functions, and the front end uses PDF.JS or image display components to preview and view PDF files.

[0015] Preferably, step S5 includes: docking configuration processing, the docking methods with each CA service provider include intra-domain privatized deployment API docking, extra-domain cloud API docking and intra-domain and extra-domain combined docking; application function API function docking, providing certificate registration and query, user and enterprise registration and query functions; callback interface function definition, processing asynchronous information callbacks provided by each CA service provider; compensation mechanism and log record processing, real-time saving of processing logs and periodic retries and active queries; network security configuration, ensuring the security of relevant files, seal access links and the confidentiality of account password keys.

[0016] The electronic signature service system compatible with multiple CA certificates provided by the present invention includes:

[0017] Certificate management module: realizes the functions of applying, deleting, modifying and viewing certificates, and adds application verification, payment and interactive callback functions;

[0018] Seal management module: realize the functions of adding, deleting, modifying, viewing and verifying user seals;

[0019] Signing rule configuration module: for different types of contracting business, pre-define the number of signatories and signing methods, set the seal type, seal number and seal page position;

[0020] Unified signing operation interface: Before calling the certificate to sign the document, all normative operations are regulated by preset rules. When signing, the application function API of different CA service providers is called according to the CA digital certificate selected by the user, or the signing request is sent to the interface to complete the actual signing;

[0021] Signing interaction docking module: realizes the functional docking of the local application function API with each CA service provider.

[0022] Preferably, the certificate management module includes: collecting CA service provider mark, company name, legal person name and application document through common field information, realizing personalized information collection according to different CA digital certificates; realizing verification, payment and interactive callback by calling different API interfaces and processing procedures according to different CA service providers; embedding the platform operation function of verifying the unified application information in the certificate application submission link;

[0023] The seal management module includes: uploading a set of seals to different CA service provider signing systems; binding the effective certificate list with the platform certificate record, and saving the seal ID returned by each CA service provider; presetting seals for initializing signatures or configuring real seals when signing automatically.

[0024] Preferably, the signing rule configuration module includes: defining the number of signatories as unilateral, bilateral or multi-party, and defining the signing order; setting a certain signatory to sign automatically or manually, and automatic signing requires signing an authorization letter and setting the CA digital certificate selected for automatic signing; specifying the type, quantity and position of the seal, and controlling whether manual dragging or not allowing the seal position to be dragged; defining the filling in of the cover information of the predetermined document before signing the contract and automatically generating merge rules.

[0025] Preferably, the unified signing operation interface includes: the operations of the unified signing interface are signed in sequence according to the signing order, and the signing initiator is the first signatory by default; all CA digital certificates are selected when the first party signs, or the signing initiator sets the CA digital certificate service provider by default or forcibly specifies it; the unified signing interface accesses the personalized requirements of the CA service provider according to user needs and security requirements; the JAVA version of itext component is used to realize the signing document and seal and dynamic page generation and merging, PDF parsing image functions, and the front end uses PDF.JS or image display components to preview and view PDF files.

[0026] Preferably, the signing interaction docking module includes: docking configuration processing, the docking methods with each CA service provider include intra-domain private deployment API docking, extra-domain cloud API docking and intra-domain and extra-domain combined docking; application function API function docking, providing certificate registration and query, user and enterprise registration and query functions; callback interface function definition, processing asynchronous information callbacks provided by each CA service provider; compensation mechanism and log record processing, real-time saving of processing logs and regular retries and active queries; network security configuration, ensuring the security of relevant files, seal access links and the confidentiality of account password keys.

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

[0028] The present invention provides an electronic signature service system that is compatible with multiple CA certificates. It can be connected to all regular CA digital certificates and service provider API interfaces currently on the market, and can provide users in the platform with a unified operation interface and process. It can meet the vast majority of online business contract signing scenarios to the greatest extent, and can flexibly respond to different API services and personalized requirements of multiple CA digital certificates and providers, thus meeting various contract signing scenarios and process specifications of existing users to the greatest extent. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Other features, objects and advantages of the present invention will become more apparent from the detailed description of non-limiting embodiments made with reference to the following drawings:

[0030] Figure 1 It is a schematic diagram of the workflow of the present invention;

[0031] Figure 2 The figure is a flow chart of the process from making a document template to generating a PDF document in the present invention. DETAILED DESCRIPTION

[0032] The present invention is described in detail below in conjunction with specific embodiments. The following embodiments will help those skilled in the art to further understand the present invention, but are not intended to limit the present invention in any form. It should be noted that, for those of ordinary skill in the art, several changes and improvements can also be made without departing from the concept of the present invention. These all belong to the protection scope of the present invention.

[0033] Example 1

[0034] The present invention provides an electronic signature service method compatible with multiple CA certificates, comprising:

[0035] Step S1: Create a certificate management module to implement basic editing functions such as certificate application, deletion, modification, and viewing, and add application verification, payment, interactive callback and other functions.

[0036] The certificate application form has common field information, including CA service provider mark, company name, company unified social credit code (tax number), legal person name, legal person ID card, company address, applicant name, applicant mobile phone number, applicant ID card number and other basic information and application documents. Personalized information collection and document collection can be realized according to the selection of different CA digital certificates. Personalized information refers to the key information required by each CA supplier for users to apply for registration, such as email account, address, various identity certificate codes and other unique information, as well as scanned copies of authorization seals, and scanned copies of personal identity and company business certificates. In the development process, the pre-configured data structure is bound to different CA service provider marks, and the dynamic JSON data structure is converted and parsed to realize dynamic display, collection, and storage of information in the UI interface. Finally, the CA digital certificate application interface input structure provided by the CA supplier is adapted and filled in and submitted to meet the requirements of the registration application.

[0037] 2. The platform certificate record is the most fundamental basis for distinguishing different CA digital certificate service providers. After successfully applying for a certificate through the API interface and page jump to the signing system of each CA service provider, it will call back and bind the certificate identifiers of different CA digital certificate service providers.

[0038] 3. Different verification, payment, and interactive callbacks also call different API interfaces and processing procedures according to different CA service providers.

[0039] 4. When submitting certificate application materials, platform operation functions such as unified information of inspection application can also be embedded to ensure the standard requirements of application materials.

[0040] 5. Certificate types are divided into corporate certificates and personal certificates according to the nature of the subject, and are divided into Ukey (hard) signatures and soft signatures according to the nature of the carrier.

[0041] Step S2: Create a seal management module to implement basic functions such as adding, deleting, modifying, viewing, and verifying user seals.

[0042] 1. Implement a set of seals within the platform, which can be uploaded to the signing systems of different CA service providers respectively.

[0043] 2. Locate the seal. The user manually selects the corresponding effective certificate list to form a binding relationship with the platform certificate record, and saves the seal ID returned by each CA service provider for signature identification. In subsequent use, the corresponding signing seal can be dynamically selected according to the binding relationship between the seal and each CA digital certificate, following the use of the CA digital certificate.

[0044] 3. The signing rule configuration can preset seals for initial signing or configuring real seals for automatic signing.

[0045] Step S3: Create a signing rule configuration module, which is mainly used to deal with different types of signing businesses with high repetitiveness and standardized processes, especially some automatic signing modes. Preset signing rules can improve signing efficiency and standard requirements. Usually, there are pre-defined number of signatories, signing method, and setting of seal type, number of seals, and seal page position.

[0046] 1. Signing rules enable users to define a set of rules on the platform. Each set of rules generates a unique code, which can be parsed and applied in the subsequent final signing process. The processing logic of the parsing application is: when uploading the data records and files to be signed, the signing rule code will be pre-bound. Through the signing rule code, when the records to be signed are imported through the platform system standard record API interface and subsequently transferred to each signatory, the corresponding signing rules are queried, and the CA data certificate required by the rules, the type of seal used for signing, the page number where the seal is placed, the number of seals, the position of the seal, whether the position is allowed to be changed, and other rule definitions are parsed in turn. On the one hand, the relevant parameter data of the record to be signed is initialized, and on the other hand, the verification condition value of this signing is formed, so as to perform logical judgment in the front-end and back-end preset codes to achieve the signing control effect. For example, whether the seal type dragged by the user when signing is a special seal for the contract, whether it is placed on a specific page, and whether the seal is stamped by keywords, etc. In addition, the most important thing is that in the signing rules bound to the record to be signed, the configured CA digital certificate can determine which CA digital certificate each signatory uses to complete the signing process. In this way, by binding different signing rules to the records to be signed and binding different CA digital certificates with different rules, dynamic compatibility with multiple CA digital certificates can be achieved.

[0047] 2. The number of signatories can be defined as single-party signature, double-party signature, or multiple-party signature, and the signing order can be defined.

[0048] 3. The signing method can be set to automatic signing or manual signing by a certain signatory, but automatic signing requires signing a power of attorney and setting up the CA digital certificate selected for automatic signing.

[0049] 4. Seal type, quantity, position, etc. are used to indicate what type of seal, how many or how many seals to place on the signing document page, and on which page positions to place them, etc., to facilitate default settings when signing, and to control whether the seal position can be manually dragged or not, and to automatically find and locate based on keywords in the file, etc.

[0050] 5. In addition, you can define rules for filling in the cover information of the scheduled documents and automatically generating and merging them before the contract is signed.

[0051] 6. You can set specific signing rules for individual companies, etc.

[0052] Step S4: Create a unified signing operation interface. Before calling the certificate to sign the document, all normative operations are regulated by the platform rules. During the final signing, the API of different CA service providers is called according to the CA digital certificate selected by the user, or the signing request is sent to the jump interface to complete the actual signing.

[0053] 1. The unified signing operation interface and process are the same for users using different CA digital certificates. The default main functions are selecting CA digital certificates, viewing documents to be signed, dragging and dropping or replacing seals, signing authentication verification, signing preview, etc. After finally collecting the signing-related information, it will be sent to the corresponding CA digital certificate signing service.

[0054] 2. Operations in the unified signing interface are signed in sequence according to the signing order. The signing initiator is the first signatory by default. The signing order of the signatories can be configured through the signing rules.

[0055] 3. When the first party signs, all CA digital certificates for the contract can be freely selected by default. The signing initiator can also set the CA digital certificate service provider by default or forcibly specify it through signing rules.

[0056] 4. The most important effect of the unified signing interface is to simplify and standardize the signing operation, shield the personalized operation interface of each CA digital certificate signing system, reduce the user's learning time cost, and improve the user's signing efficiency and experience.

[0057] 5. The unified signing interface can also be connected to the personalized requirements of CA service providers in a specific environment according to user needs and security requirements, such as jump page, user authentication method, etc.

[0058] 6. The main application technology of the unified signing interface is to use the JAVA version of itext components to realize functions such as signing documents and seals, dynamic page generation and merging, PDF parsing images, etc. The front end uses PDF.JS or image display components to preview and view PDF files, so that what you see is what you get.

[0059] Step S5: Sign the interactive docking module. Implement the API and links, monitoring callback methods, personalized logic processing, etc. provided by the platform and various CA service providers.

[0060] 1. Connection configuration processing. According to the needs and file security requirements, the connection methods with various CA service providers are generally private deployment API connection within the domain, cloud API connection outside the domain, and combined connection within and outside the domain. It is necessary to configure relevant connection parameters such as system address, account password, encryption and decryption key, file path, etc.

[0061] 2. Application API function docking. Each CA service provider provides certificate registration and query, user and enterprise registration and query, seal upload and query, file upload and query, signature submission and query, signature verification application and query and other main functions, which are assembled and configured according to different field structures, parameters and logical processing.

[0062] 3. Definition of callback interface function. Each CA service provider provides callbacks for asynchronous information such as certificate approval results, seal upload results, authorization results, security authentication results, and signing results. The platform provides personalized processing of the above callback result fields and parameter values, security verification, and callback source identification, and finally converts them into unified result information to perform logical processing on the certificate application, seal record, and signature record used for electronic signature, and correctly reflects the processing results of CA services from different sources. The logic for converting to unified result processing is as follows: 1. Classify according to certificate approval callback, seal upload, authentication callback, signing completion, etc., and define the target common data structure of each classification. 2. Since the API and parameter data structure field names provided by each CA service provider are not the same, hard-coded processing such as one-to-one assignment or conversion according to Chinese names is used. 3. Save the original received data and the converted result records to form a log.

[0063] 4. Compensation mechanism and log record processing. Depending on the docking method, there is asynchronous processing logic with the external system. In order to track and compensate for transaction processing, the processing log is saved in real time, and conditional queries are made to the list of certificates to be approved, seals to be approved, records to be signed, etc. According to the needs, asynchronous calls are made to the corresponding CA service provider API interface through polling every 5, 10 minutes or at 23:00 at night to retry and actively query, so that the network anomaly, internal and external system anomaly, data anomaly, etc. can be correctly processed as soon as possible after recovery.

[0064] 5. Network security configuration, etc. Electronic signatures have extremely high security requirements and require correct configuration of the network, server, and firewall. Access links for related documents, seals, etc. need to be converted into short links in garbled format, and account passwords and keys cannot be displayed in plain text.

[0065] Example 2

[0066] The present invention also provides an electronic signature service system compatible with multiple CA certificates. The electronic signature service system compatible with multiple CA certificates can be implemented by executing the process steps of the electronic signature service method compatible with multiple CA certificates, that is, those skilled in the art can understand the electronic signature service method compatible with multiple CA certificates as a preferred implementation of the electronic signature service system compatible with multiple CA certificates.

[0067] The electronic signature service system compatible with multiple CA certificates provided in accordance with the present invention includes: a certificate management module: realizing the application, deletion, modification and viewing functions of certificates, and adding application verification, payment and interactive callback functions; a seal management module: realizing the addition, deletion, modification, viewing and verification functions of user seals; a signing rule configuration module: pre-defining the number of signatories and signing methods for different types of contracting businesses, setting the seal type, number of seals and seal page position; a unified signing operation interface: before calling the certificate to sign the document, all normative operations are regulated by preset rules, and at the final signing, the application function API of different CA service providers is called according to the CA digital certificate selected by the user, or the signing request is sent to the jump interface to complete the actual signing; a signing interactive docking module: realizing the functional docking between the local and the application function APIs of each CA service provider.

[0068] The certificate management module includes: collecting CA service provider mark, company name, legal person name and application document through common field information, realizing personalized information collection according to different CA digital certificates; realizing verification, payment and interactive callback by calling different API interfaces and processing procedures according to different CA service providers; embedding the platform operation function of verifying the unified application information in the certificate application submission link;

[0069] The seal management module includes: uploading a set of seals to different CA service provider signing systems; binding the effective certificate list with the platform certificate record, and saving the seal ID returned by each CA service provider; presetting seals for initializing signatures or configuring real seals when signing automatically.

[0070] The signing rule configuration module includes: defining the number of signatories as unilateral, bilateral or multi-party, and defining the signing order; setting a certain signatory to sign automatically or manually, and automatic signing requires signing an authorization letter and setting the CA digital certificate selected for automatic signing; specifying the seal type, quantity and position, and controlling whether manual dragging or not allowing dragging of the seal position; defining the filling in of the cover information of the predetermined document before signing the contract and automatically generating merge rules.

[0071] The unified signing operation interface includes: the operations of the unified signing interface are signed in sequence according to the signing order, and the signing initiator is the first signer by default; all CA digital certificates are selected when the first party signs, or the signing initiator sets the CA digital certificate service provider by default or forcibly specifies it; the unified signing interface is connected to the personalized requirements of the CA service provider according to user needs and security requirements; the JAVA version of itext component is used to realize the signing document and seal and dynamic page generation and merging, PDF parsing image functions, and the front end uses PDF.JS or image display components to preview and view PDF files.

[0072] The signing interaction docking module includes: docking configuration processing, the docking methods with each CA service provider include intra-domain private deployment API docking, extra-domain cloud API docking and intra-domain and extra-domain combined docking; application function API function docking, providing certificate registration and query, user and enterprise registration and query functions; callback interface function definition, processing asynchronous information callbacks provided by each CA service provider; compensation mechanism and log record processing, real-time saving of processing logs and regular retries and active queries; network security configuration, ensuring the security of relevant files, seal access links and the confidentiality of account password keys.

[0073] Those skilled in the art know that, in addition to implementing the system, device and its various modules provided by the present invention in a purely computer-readable program code, it is entirely possible to implement the same program in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers and embedded microcontrollers by logically programming the method steps. Therefore, the system, device and its various modules provided by the present invention can be considered as a hardware component, and the modules included therein for implementing various programs can also be considered as structures within the hardware component; the modules for implementing various functions can also be considered as both software programs for implementing the method and structures within the hardware component.

[0074] The above describes the specific embodiments of the present invention. It should be understood that the present invention is not limited to the above specific embodiments, and those skilled in the art can make various changes or modifications within the scope of the claims, which does not affect the essence of the present invention. In the absence of conflict, the embodiments of the present application and the features in the embodiments can be combined with each other arbitrarily.

Claims

1. An electronic signature service method compatible with multiple CA certificates, characterized in that: include: Step S1: Create a certificate management module to implement certificate application, deletion, modification and viewing functions, and add application verification, payment and interactive callback functions; Step S2: Create a seal management module to implement the functions of adding, deleting, modifying, viewing and verifying user seals; Step S3: Create a signing rule configuration module, predefine the number of signatories and signing methods for different types of signing services, and set the seal type, seal number, and seal page position; Step S4: Create a unified signing operation interface. Before calling the certificate to sign the document, all normative operations are regulated by preset rules. When signing, the application function API of different CA service providers is called according to the CA digital certificate selected by the user, or the signing request is sent to the interface to complete the actual signing; Step S5: Create a signing interaction docking module to achieve functional docking between the local application function API and the application function API of each CA service provider.

2. The electronic signature service method compatible with multiple CA certificates according to claim 1, characterized in that: The step S1 includes: collecting CA service provider mark, company name, legal person name and application document through common field information, and realizing personalized information collection according to selecting different CA digital certificates; realizing verification, payment and interactive callback by calling different API interfaces and processing procedures according to different CA service providers; embedding a platform operation function for verifying the unified application information in the certificate application submission link; The step S2 includes: uploading a set of seals to different CA service providers' signing systems; binding the effective certificate list with the platform certificate record, and saving the seal IDs returned by each CA service provider; and presetting the seal for initializing the signature or configuring the real seal when signing automatically.

3. The electronic signature service method compatible with multiple CA certificates according to claim 1, characterized in that: The step S3 includes: defining the number of signatories as unilateral, bilateral or multi-party, and defining the signing order; setting a certain signatory to sign automatically or manually, and the automatic signing requires signing a power of attorney and setting the CA digital certificate selected for the automatic signing; specifying the seal type, quantity and position, and controlling whether manual dragging or not is allowed for the seal position; defining the filling in of the cover information of the predetermined document before signing the contract and automatically generating merge rules.

4. The electronic signature service method compatible with multiple CA certificates according to claim 1, characterized in that: The step S4 includes: the operations of the unified signing interface are signed in sequence according to the signing order, and the signing initiator is the first signer by default; all CA digital certificates are selected when the first party signs, or the signing initiator sets the CA digital certificate service provider by default or forcibly specifies it; the unified signing interface is connected to the personalized requirements of the CA service provider according to user needs and security requirements; the JAVA version of itext component is used to realize the signing document and seal and dynamic page generation and merging, PDF parsing image functions, and the front end uses PDF.JS or image display components to preview and view PDF files.

5. The electronic signature service method compatible with multiple CA certificates according to claim 1, characterized in that: The step S5 includes: docking configuration processing, the docking methods with each CA service provider include intra-domain private deployment API docking, extra-domain cloud API docking and intra-domain and extra-domain combined docking; application function API function docking, providing certificate registration and query, user and enterprise registration and query functions; callback interface function definition, processing asynchronous information callbacks provided by each CA service provider; compensation mechanism and log record processing, real-time storage of processing logs and regular retries and active queries; network security configuration, ensuring the security of relevant files, seal access links and the confidentiality of account password keys.

6. An electronic signature service system compatible with multiple CA certificates, characterized in that: include: Certificate management module: realizes the functions of applying, deleting, modifying and viewing certificates, and adds application verification, payment and interactive callback functions; Seal management module: realize the functions of adding, deleting, modifying, viewing and verifying user seals; Signing rule configuration module: for different types of contracting business, pre-define the number of signatories and signing methods, set the seal type, seal number and seal page position; Unified signing operation interface: Before calling the certificate to sign the document, all normative operations are regulated by preset rules. When signing, the application function API of different CA service providers is called according to the CA digital certificate selected by the user, or the signing request is sent to the interface to complete the actual signing; Signing interaction docking module: realizes the functional docking of the local application function API with each CA service provider.

7. The electronic signature service system compatible with multiple CA certificates according to claim 6, characterized in that: The certificate management module includes: collecting CA service provider mark, company name, legal person name and application document through common field information, realizing personalized information collection according to different CA digital certificates; realizing verification, payment and interactive callback by calling different API interfaces and processing procedures according to different CA service providers; embedding the platform operation function of verifying the unified application information in the certificate application submission link; The seal management module includes: uploading a set of seals to different CA service provider signing systems; binding the effective certificate list with the platform certificate record, and saving the seal ID returned by each CA service provider; presetting seals for initializing signatures or configuring real seals when signing automatically.

8. The electronic signature service system compatible with multiple CA certificates according to claim 6, characterized in that: The signing rule configuration module includes: defining the number of signatories as unilateral, bilateral or multi-party, and defining the signing order; setting a certain signatory to sign automatically or manually, and automatic signing requires signing an authorization letter and setting the CA digital certificate selected for automatic signing; specifying the seal type, quantity and position, and controlling whether manual dragging or not allowing dragging of the seal position; defining the filling in of the cover information of the predetermined document before signing the contract and automatically generating merge rules.

9. The electronic signature service system compatible with multiple CA certificates according to claim 6, characterized in that: The unified signing operation interface includes: the operations of the unified signing interface are signed in sequence according to the signing order, and the signing initiator is the first signer by default; all CA digital certificates are selected when the first party signs, or the signing initiator sets the CA digital certificate service provider by default or forcibly specifies it; the unified signing interface is connected to the personalized requirements of the CA service provider according to user needs and security requirements; the JAVA version of itext component is used to realize the signing document and seal and dynamic page generation and merging, PDF parsing image functions, and the front end uses PDF.JS or image display components to preview and view PDF files.

10. The electronic signature service system compatible with multiple CA certificates according to claim 6, characterized in that: The signing interaction docking module includes: docking configuration processing, the docking methods with each CA service provider include intra-domain private deployment API docking, extra-domain cloud API docking and intra-domain and extra-domain combined docking; application function API function docking, providing certificate registration and query, user and enterprise registration and query functions; callback interface function definition, processing asynchronous information callbacks provided by each CA service provider; compensation mechanism and log record processing, real-time saving of processing logs and regular retries and active queries; network security configuration, ensuring the security of relevant files, seal access links and the confidentiality of account password keys.

Images