Bangladesh computer council delivers e-signing to citizens with Ascertia’s solutionsBy csc |
Trust Service Providers (TSPs) and Qualified Trust Service Providers (QTSPs) are using CSC globally to enable users to sign documents using Qualified and Advanced Electronic Signatures. With every country having its own requirements and regulations, CSC is enabling TSPs to offer interoperable solution offerings. This provides users with a choice of signature providers, ensuring solutions can adhere to industry standard requirements and offer ultimate flexibility for customers.
This is a benefit for many TSPs but especially in countries where choice is a legal requirement. In Chile, the fair competition law requires companies to offer equal opportunities for companies to partake in solution offerings. CSC’s API enables TSPs in the country to offer certificates and signing from multiple providers, adhering to this law but also ensuring customers receive a tailored approach that is not limited by compatibility or integration requirements.
In Europe, with the eIDAS regulation, QTSPs are using CSC as part of their PKI infrastructures to natively integrate with multiple signing servers and signature solutions to provide a wide choice of eIDAS compliant signatures.
Ascertia works with multiple Enterprise, government organisations, TSPs and QTSPs globally. Ensuring our products are compatible with the latest CSC API ensures we can provide even greater integration and interoperability to our customers, and the TSPs that use us to deliver their services.
This includes the Bangladesh Computer Council (BCC), a government organisation and licensed Certificate Authority in Bangladesh that is part of the country’s Digital Bangladesh initiative.
As part of the digital transformation of the country, BCC searched for solutions that could provide electronic signature services for Bangladesh’s citizens as well as timestamping services for businesses and the government and it chose Ascertia’s solutions.
SigningHub and ADSS Server are both CSC v188.8.131.52 compliant which future proofs the solution to allow integration with additional signing solutions and TSPs.
You can read the full case study here.