This article maps the full digital signature journey from initial document submission to final archiving, demonstrating how Virifi’s Solution Proposal adapts to both Proof-of-Concept (POC) scenarios and scalable real-world applications for financial institutions.
1. Introduction
This article describes the complete user journey when interacting with Virifi's Solution Proposal within the Central Bank of Jordan (CBJ) PKI trust framework. It includes both the Proof-of-Concept (POC) demonstration flow and potential real-world applications that financial institutions can implement using the provided SDKs and APIs.
2. POC User Journey (Demonstration Flow)
The current demonstration apps (Web, Android, iOS) simulate the foundational signature process. The user journey includes the following steps:
2.1 Document Preparation
User selects or uploads the document requiring a digital signature.
Supported file types: PDF, XML, JSON, CMS packages.
2.2 Authentication and Authorization
User authenticates using a CBJ-issued client certificate (via mutual TLS) or token-based access.
The backend verifies the user's authorization and signing permissions.
2.3 Signature Initiation
User selects the signing mode:
Single signer
Multiple signers (Parallel or Sequential)
Document is uploaded to secure storage or directly to the HSM-backed signing service.
2.4 Cryptographic Signing
Signing operation occurs:
Using a Cloud HSM, On-Prem HSM, or local device key (e.g., YubiKey).
Signature is generated in the selected format (PAdES, XAdES, CAdES, or JAdES).
Trusted timestamping is applied if B-T, LT, or LTA levels are requested.
2.5 Signature Validation
System automatically validates:
Signature structure
Certificate trust chain to CBJ Root CA
Revocation status via OCSP/CRL services
2.6 Document Retrieval and Archiving
Signed documents are available for retrieval.
Documents can be archived with long-term validation attributes (LTA) when required.
3. Real-World Applications and Advanced Journeys
Virifi's Solution Proposal enables financial institutions and service providers to extend beyond the demonstration flows and implement robust real-world use cases.
3.1 Automated Financial Document Signing
Documents such as loan agreements, account mandates, or transaction approvals can be signed through fully automated workflows.
Multi-party signing: branch manager, compliance officer, customer.
Auto-validation and secure long-term archival.
3.2 Customer Onboarding and Account Opening Forms
Customers fill and sign onboarding forms digitally.
Mobile or web apps authenticate users and apply digital signatures.
Biometrics (Face ID, Touch ID) may be used to enhance user authentication.
Signed forms are validated and integrated into core banking systems.
3.3 Long-Term Legal Contract Signing and Archiving
Critical documents requiring long-term legal enforceability are signed using LTA profiles.
Periodic revalidation via CBJ Timestamping Authority (TSA) ensures decades-long signature validity.
3.4 Internal Approvals and Regulatory Compliance
Staff HR forms, internal approvals, risk reports, and audit trails are signed and managed securely.
Sequential or parallel signing flows are supported for collaborative review and approval cycles.
Full logging and auditability ensure compliance with internal and external regulatory bodies.
4. Notes
The SDKs and APIs provided by Virifi are modular and adaptable.
Institutions can tailor workflows to meet specific business or regulatory needs.
Signature flows can be fully automated, semi-automated, or user-driven.
All operations are compliant with CBJ trust policies and ETSI eIDAS standards.
5. Summary
Virifi's Solution Proposal provides a flexible, standards-compliant framework that enables secure digital signature operations at all levels, from simple document signing demonstrations to complex, institution-wide financial workflows. This adaptability ensures that financial institutions can meet evolving regulatory demands while enhancing operational efficiency and user experience.