Digital signatures in Chile: what is FirmaGob and how to integrate it into your system

The problem: documents that still travel on paper

In 2026, thousands of Chilean public institutions still send official documents on paper. A document that requires the signature of a department head, approval from a legal department, and dispatch to another government entity can take days — sometimes weeks — to complete its cycle.

The problem is not just the slowness. It's the lack of traceability: who signed? When? Is the document that arrived the same one that was sent? Without a legally valid digital signature, these questions have no verifiable answer.

What is FirmaGob?

FirmaGob is the advanced electronic signature platform of the Chilean State, managed by the Digital Government Division of the Ministry of the General Secretariat of the Presidency. It allows public officials to sign documents with legal validity equivalent to a handwritten signature, according to Law 19,799 on electronic documents and electronic signatures.

Unlike tools such as DocuSign or Adobe Sign, FirmaGob has two unique characteristics:

• Full legal validity in Chile: FirmaGob's advanced signature is backed by a provider accredited by the Ministry of Economy, giving it the same legal force as a notarized signature.
• Free for the State: any public official can sign at no cost, eliminating the adoption barrier.

The architecture: FirmaGob + DocDigital + ClaveUnica

FirmaGob doesn't work alone. In practice, a modern document management system for the Chilean State needs to integrate three platforms:

1. FirmaGob— advanced electronic signature. The user submits a document (usually PDF), FirmaGob applies the cryptographic signature and returns the signed document with its certificate. The API supports single and multiple signatures (several people signing the same document).

2. DocDigital— official document transmission. Once signed, the document must reach its recipient in a verifiable way. DocDigital is the State's platform for official transmission between institutions. It connects over 5,000 public entities with full traceability: who sent it, who received it, when, and the document's hash.

3. ClaveUnica— identity authentication. For an official to sign, they must first authenticate. ClaveUnica is the State's digital identity system (equivalent to Login.gov in the U.S. or cl@ve in Spain). It uses OAuth2 and provides the user's verified RUT.

Technical integration: what no one tells you

The official documentation for these APIs exists, but it is scattered and sometimes outdated. After integrating all three platforms into a real system, these are the lessons we learned:

FirmaGob uses SOAP, not REST.Yes, in 2026. The signing API is based on WSDL/SOAP with XML. If your stack is modern (Node.js, Python, Go), you need a wrapper that handles XML serialization. It's not complex, but it is unexpected for teams that have only worked with REST/JSON APIs.

DocDigital requires an institutional certificate. API credentials alone are not enough. The institution must request a specific digital certificate for transmission, which identifies the issuing organization. This process can take weeks and is the most common bottleneck in integration projects.

ClaveUnica has strict rate limits. The authentication endpoint handles millions of users nationwide and applies aggressive throttling. Your system must handle retries with exponential backoff and session token caching.

Test environments don't always mirror production. All three platforms have staging environments, but the differences with production are significant (especially in response times and certificate validation). Plan extra time for testing in the real environment.

Recommended stack

Based on our experience integrating these platforms, this is the architecture we recommend:

• Backend: NestJS (TypeScript) with Docker. Nest's modularity allows separating each integration (FirmaGob, DocDigital, ClaveUnica) into independent modules with their own tests.
• Database: PostgreSQL with full auditing. Every action (signing, sending, receiving) must be recorded with a timestamp, user, and document hash.
• Job queues: Bull/BullMQ for processing signatures and transmissions asynchronously. Government APIs have variable latencies (2–30 seconds), and you don't want your user waiting with a blocked interface.
• Authentication: OAuth2 with ClaveUnica as the primary provider, with fallback to institutional credentials for automated operations.

How much does it cost?

The government APIs are free. The real cost lies in development and infrastructure:

• Integration development: between 3 and 6 months for a small team (2–3 developers), depending on the complexity of the institution's document workflow.
• Infrastructure: a server with Docker can handle hundreds of documents daily. The hosting cost is marginal ($20–50 USD/month).
• Certificates: the institutional certificate for DocDigital has no cost, but the administrative process does consume time.

The savings are significant: an institution that processes 100 documents daily on paper can reduce processing time from days to minutes, with full traceability and no marginal cost per document.

Conclusion

Chile's government digital signature infrastructure is robust and free, but underutilized. Most public institutions don't integrate it because they lack the technical team to do so, not because the technology doesn't exist.

If your institution needs to digitize document workflows with legal signatures, the combination of FirmaGob + DocDigital + ClaveUnica is the way forward. We know because we built it.