Encryption in Transit — ConvergeX E-Invoicing

What this means for you

Encryption in transit is the protection applied while data moves across the internet or between ConvergeX services—like the lock on a courier van while documents are in delivery.

We use industry-standard TLS so your information is protected against:

Unauthorized interception

Traffic cannot be read by third parties

Data tampering

Altered payloads are detectable

Man-in-the-middle attacks

Endpoints are authenticated via TLS

You do not need to configure TLS yourself—when you use our website or API on the live production environment, secure connections are enforced by the platform.

What is encryption in transit?

Encryption in transit ensures that:

Data transmitted over networks is encrypted using secure cryptographic protocols
Communication between systems is protected from unauthorized access
Data integrity is maintained during transmission

ConvergeX uses these technologies behind the scenes:

HTTPS (TLS 1.2 / 1.3) TLS-secured PostgreSQL HTTPS object storage SMTP with STARTTLS

What connections are protected

Whenever data leaves your browser or integration and touches ConvergeX, it is covered—including:

End users and API clients accessing the system
Application server communication with backend services
Database connectivity (PostgreSQL)
Object storage interactions (e.g., AWS S3)
Email communication via SMTP
Third-party integrations and external APIs

How your data travels securely

From your browser or ERP system to our servers—and from there to the database, file storage, and email service—each hop uses TLS encryption. Your invoice and company data are not sent as plain text.

[ User / API Client ]
        │
        ▼ HTTPS (TLS 1.2 / 1.3)
[ Web / API Layer — Django Application ]
        │
        ├── TLS ──► PostgreSQL Database
        │
        ├── HTTPS ──► Object Storage (S3)
        │
        └── STARTTLS ──► SMTP Server

On the live site you should always use https:// in the address bar. We redirect insecure HTTP to HTTPS in production.

Each connection, explained simply

Your browser & API integrations (HTTPS)

When you log in, work in the portal, or send invoices via API:

Production uses HTTPS only (TLS 1.2 / 1.3)—the padlock in your browser
Session and security cookies are marked secure in production
Additional browser protections (HSTS, secure headers) reduce common web risks

If you integrate by API, use the HTTPS base URL we provide; do not send credentials over plain HTTP.

Platform to database

Your invoice and company records live in PostgreSQL. The application connects over TLS:

Production: strict verification of the database server (verify-full)
Local development: relaxed settings so engineers can test without breaking your setup

For you

Customer data is not exposed as cleartext between app servers and the database in production.

File uploads & downloads

PDFs, attachments, and generated documents use encrypted HTTPS to cloud object storage.

For you

Uploading or downloading files through ConvergeX uses the same kind of protection as online banking sites.

Emails we send you

Verification codes, notifications, and system email use STARTTLS so content is encrypted in transit to your mail provider.

Inside the platform

Internal APIs and services also communicate securely, with authentication (including MFA at login and API keys for integrations) so only authorised users and systems can act on your data.

Production vs local development

We use strong TLS everywhere that matters. The strictest browser rules apply on the live production environment:

TLS 1.2 / 1.3

Secure cookie policies

HSTS (production)

Certificate validation

Encrypted DB connections

Secure API communication

Outdated protocols (SSL, TLS 1.0, TLS 1.1) are not used on production.

In summary

Whenever you use ConvergeX in production:

Your browser and API traffic uses HTTPS (TLS 1.2+)
Database and file connections inside our cloud are encrypted
Email we send uses TLS where your provider supports it
Integrations should always target our HTTPS endpoints

We maintain certificates, review TLS settings, and apply security updates so you can focus on invoicing—not on wiring up encryption yourself. Questions? Contact our team.