Format Compatibility Overview
Virifi’s Solution Proposal supports four major electronic signature formats aligned with ETSI eIDAS standards and fully interoperable with CBJ’s PKI infrastructure. These formats cover all key use cases across frontend applications, APIs, and backend financial systems.
PAdES (PDF Advanced Electronic Signatures)
Standard: ETSI EN 319 142-1
Used For: PDF documents
Advantages: Signatures are embedded directly into the PDF and remain visible and verifiable in common tools like Adobe Acrobat. Ideal for signed contracts, regulatory forms, and legal submissions.
Signature Levels Supported: B, B-T, LT, LTA
XAdES (XML Advanced Electronic Signatures)
Standard: ETSI EN 319 132-1
Used For: Structured XML data
Advantages: Embeds the signature as part of the XML structure, supporting granular data signing. Well-suited for government workflows, e-invoicing, and XML-based contracts.
JAdES (JSON Advanced Electronic Signatures)
Standard: ETSI TS 119 182-1
Used For: API and mobile-driven transactions using JSON
Advantages: Extends the JOSE standard (JWS/JWT) to include advanced signature properties. Perfect for fintech APIs, mobile wallets, and cloud-native apps.
CAdES (CMS Advanced Electronic Signatures)
Standard: ETSI EN 319 122-1
Used For: Binary data and backend system-to-system communications
Advantages: Based on Cryptographic Message Syntax (CMS/ASN.1), widely used in secure file transfers, archiving, and message integrity validation.
Notes: Fully supported in validation services and compatible with Virifi’s signing backend.
Format Comparison Table
Format | Target | Readable in Common Tools | Use Cases |
PAdES | ✅ Adobe Acrobat | Contracts, reports | |
XAdES | XML | ⚠️ Structured viewers needed | eGov, XML data |
JAdES | JSON | ✅ Web/mobile | APIs, fintech |
CAdES | Binary | ❌ Requires parsers | Backend, archival |