---
title: "Does Web PKI support establishing SSL connections with the user's certificate?"
description: "Whether Web PKI can establish SSL connections with the user's certificate (yes, with sendAuthenticatedRequest) and how to transmit an NFe signed in the browser."
canonical: "https://docs.lacunasoftware.com/en-us/articles/web-pki/faq/ssl"
locale: "en"
product: "Web PKI"
last_updated: "2026-10-12"
---

# Does Web PKI support establishing SSL connections with the user's certificate?

Yes. Since [API 1.4](https://docs.lacunasoftware.com/en-us/articles/web-pki/api-reference/versions#v1-4), the `sendAuthenticatedRequest()` method sends web requests authenticated
with the user's certificate through mutual SSL/TLS, from the user's computer. See [Authenticated request](https://docs.lacunasoftware.com/en-us/articles/web-pki/auth-request).
To transmit an NFe, however, you usually do not need the user's certificate, as explained below.

## (or How do I to transmit a NFe to Receita/SEFAZ/prefeitura?)

Currently, it is common to use the same certificate to issue an electronic invoice and transmit it to the competent agency 
(transmission is via SSL with mutual authentication). The predominance of this architecture comes from the fact 
that the first electronic invoice signature products were mostly desktop applications. In a web system, you have to deal with 
the problem that the client certificate is not available on the backend.

To solve the problem of signing NFe in the browser, the Web PKI component fits perfectly (see the
[online example](https://www.lacunasoftware.com/en/DemoRestPKI/nfeSignature)). In the case of transmission, it is not 
necessary to use the same certificate used to issue the electronic invoice. The national standard allows a certificate issued 
to a company other than the company that issued the electronic invoice to be used for transmission.

This enables **the transmission to be done on the backend using an A1 certificate issued on behalf of the company offering the electronic invoice web signing service (your company), rather than using the NFe issuing company certificate (your client)**. This avoids the problem of transmitting the electronic invoice with a certificate available only on the frontend.