Security
Solución Factible® maintains enterprise‑grade security standards across every operational layer: from encrypted connections between our servers and client systems to the secure storage and processing of information. This ensures that your electronic invoices remain protected under modern, auditable protocols.
HTTPS/SSL Security Certificate
To safeguard connections, Solución Factible® uses TLS 1.2 and TLS 1.3 certificates issued by globally recognized Certificate Authorities. We have implemented an automated integration with Google Trust Services, enabling streamlined issuance and deployment of certificates that comply with CA/B Forum guidelines. These certificates employ state‑of‑the‑art cryptographic algorithms, including ECDSA over prime256v1 and AES‑GCM cipher suites at 128‑ and 256‑bit strength.
Depending on the service, certificates may use Domain Validation (DV) or Organization Validation (OV). It is important to note that modern browsers no longer display distinct visual indicators for Extended Validation (EV) certificates. Today, the critical factors are the validity period and the complete trust chain, rather than visual symbols such as padlocks or colored address bars.
For environments that require manual installation, we provide a dedicated link where clients can download the most recent SSL certificate. Each certificate remains valid for three months from its issuance date and is available for both Testing and Production environments. These downloads are intended for cases where automated retrieval is not possible or where specialized installation processes are required by your IT staff.
For more detail about this change, review this URL.
How to verify a Secure Connection
To view the site's connection details using a web browser, click the icon that appears to the left of the web address. This will display a summary of the connection details, where you can confirm that the connection is secure and view more details about the certificate used for the connection such as:
- Certificate issuer (e.g., Google Trust Services).
- Public key algorith (e.g., ECDSA P‑256 or RSA with SHA‑256).
- Validity period (start and expiration dates).
- Trust chain up to the root CA.
This ensures that you are connected to the legitimate Solución Factible® website and that the information transmitted between you and your computer is protected in accordance with international standards.
For transparency, we also provide a historical record of public SSL certificates previously used to establish secure HTTPS connections with our Production and Testing servers.
Historical SSL certificates used in Production: |
|||
| Download link | Description | Intermediaries | Validity |
| prod2024-2025.cer | The certificate that the server sends for identification and for the encryption of the communication. | prodbundle2024-2025.cer | September 13, 2025. |
| server2024.cer | The certificate that the server sends for identification and for the encryption of the communication. | bundle_prod_2024.crt | October 14, 2024. |
| server2023.cer | The certificate that the server sends for identification and for the encryption of the communication. | bundle2023.cer | September 25, 2023. |
| server_2022.cer | The certificate that the server sends for identification and for the encryption of the communication. | bundle_2022.cer | November 16, 2022. |
|
solucionfactible_com_ 15102020-16112021.cer |
The certificate that the server sends for identification and for the encryption of the communication. |
solucionfactible_com_ 01112018-31122030.cer-root |
November 16, 2021. |
|
solucionfactible_com_ 16102018-14122020.cer |
The certificate that the server sends for identification and for the encryption of the communication. |
solucionfactible_com_ 16102018-14122020.cer-root |
December 18, 2020. |
| solucionfactible.com 2017-2018.cer | The certificate that the server sends for identification and for the encryption of the communication. | COMODORSA-ExtendedValidationSecureServer-CA | November 15, 2018. |
| solucionfactible.com_2014-2016.cer | The certificate that the server sends for identification and for the encryption of the communication. | tawte-IntermediateCA.crt | November 12, 2016. |
| sf-server.cer | The certificate that the server sends for identification and for the encryption of the communication. | thawte-server.ca-bundle | November 13, 2014. |
Historical SSL certificates used in Testing: |
|||
| Download link | Description | Intermediaries | Validity |
| testing202608.cer | The certificate that the server sends for identification and for the encryption of the communication. | testingbundle202608.cer | November 15, 2026. |
| testing2024-2025.cer | The certificate that the server sends for identification and for the encryption of the communication. | testingbundle2024-2025.cer | September 13, 2025. |
| testing2024.cer | The certificate that the server sends for identification and for the encryption of the communication. | bundle_test_2024.crt | October 14, 2024. |
| testing_server2023.cer | The certificate that the server sends for identification and for the encryption of the communication. | testing_bundle2023.cer | September 30, 2023. |
| testing_server_2022.cer | The certificate that the server sends for identification and for the encryption of the communication. | testing_bundle_2022.cer | November 16, 2022. |
| testing_solucionfactible_com_15102020-16112021.cer | The certificate that the server sends for identification and for the encryption of the communication. | testing_solucionfactible_com_01112018-31122030.cer-root | November 16, 2021. |
| testing_solucionfactible_com_2018_2019.crt | The certificate that the server sends for identification and for the encryption of the communication. | testing_solucionfactible_com_2018_2019.ca-bundle | January 13, 2021. |
| testing.solucionfactible.com 2017-2018.cer | The certificate that the server sends for identification and for the encryption of the communication. | COMODORSA-ExtendedValidationSecureServer-CA | November 26, 2018. |
| testing.solucionfactible.com_2014-2016.cer | The certificate that the server sends for identification and for the encryption of the communication. | tawte-IntermediateCA.crt | October 20, 2016.. |