sequenceDiagram
participant Signer
participant System
participant InternalDB as Internal Database
participant AtlassianDBatlassianAPI as Atlassian Database
participant HSM
participant AATL
participant TSA as Timestamping Authority
participant Stakeholders
Note over Signer,System: Signing Procedure Begins
Signer->>System: Provide Signature Data (Contract ID, Signer ID, OTP)
System->>InternalDB: Fetch Metadata (Contract Hash, Signer Data, Attachments)
System->>System: Verify Signer Credentials and Contract Signability
System->>AtlassianDB>>atlassianAPI: Fetch Contract HTML Content
System->>System: Verify the downloaded HTML's Contenthash forwith Consistencythe andstored Integrityhash
System->>System: Embed Signer Details (Signatures, Field Values) into HTML
System->>AtlassianDB>>atlassianAPI: Store Updated Contract Data
System->>HSM: Digitally Sign Contract PDF using Private Key
HSM-->>System: Signed PDF
System->>AATL: Validate Signature with Adobe Trust List
AATL-->>System: Validation Successful
System->>TSA: Timestamp the PDF (LTV)
TSA-->>System: Timestamped PDF
System->>InternalDB: Store Updated Files and Metadata
System->>Stakeholders: Notify via Webhook and Email
Note over Signer,System: Signing Procedure Complete
Note over System: Data Storage
System->>InternalDB: Store Contract Configuration Metadata, Audit Logs, Access Keys, Signer Metadata
System->>AtlassianDB>>atlassianAPI: Store Contract HTML Content, Generated PDFs
Note over System: Signature Certification
System->>HSM: Manage Private Key Storage for Secure Signing
System->>AATL: Ensure Signatures use Trusted Certificate Chains
System->>TSA: Append Timestamping and Validation Information
|