Last updated: November 4, 2026 · Reviewed by BOLD VAN's EDI team
In This Article
Quick Answer
HTTPS (HyperText Transfer Protocol Secure) is the encrypted version of HTTP. It uses TLS to encrypt data while it travels and a certificate to verify the server's identity. In EDI, HTTPS is one of several encrypted ways to exchange documents with trading partners over the internet, along with AS2 and SFTP. Plain HTTP and plain FTP are not encrypted and should not be used for business documents.
Definition
HTTPS (HyperText Transfer Protocol Secure) is a protocol for secure communication between computers over the internet. It is HTTP combined with TLS (Transport Layer Security), which encrypts data in transit and verifies the identity of the server. HTTPS is the same protocol shown at the start of a secure website's address in your browser, and it typically runs on port 443.
A protocol is a set of rules that computer applications follow to exchange data. HTTPS is the secure version of HTTP, the protocol used to request and send data across the web. HTTP was created by Tim Berners-Lee at CERN starting in 1989 and was later standardized through the Internet Engineering Task Force (IETF) and the World Wide Web Consortium (W3C).
Businesses rely on HTTPS for online payments, web applications and APIs, and it is also a common way to exchange electronic data interchange (EDI) documents, such as purchase orders and invoices, between trading partners.
HTTPS protects data in two ways: it verifies who you are connecting to, and it encrypts what you send. When a connection starts, the two computers perform a TLS handshake:
Standard HTTPS verifies only the server. In some B2B setups, both sides present certificates, which is called mutual TLS (mTLS).
The difference is security. HTTP sends data in plain text with no identity check, while HTTPS encrypts data with TLS and verifies the server with a certificate.
| HTTP | HTTPS | |
|---|---|---|
| Encryption | None; data travels in plain text | Encrypted in transit with TLS |
| Identity verification | None | Server verified by a TLS certificate |
| Default port | 80 | 443 |
| Browser display | Often marked "Not secure" | Padlock icon |
| Suitable for EDI? | No | Yes |
Yes. HTTPS is a common way to exchange EDI documents over the internet, especially through web services and APIs. It is also the foundation of AS2, one of the most widely used EDI methods in retail, which runs over HTTP or HTTPS and adds its own message encryption, digital signatures and delivery receipts.
Many businesses exchange EDI through a value-added network (VAN), which routes documents between trading partners and manages the connections for them. Whether you connect to a VAN or directly to a trading partner, the connection should use an encrypted method such as HTTPS, AS2 or SFTP.
Keep in mind that HTTPS protects data in transit. Protecting data once it is stored requires separate encryption at rest.
HTTPS is one of several ways to move EDI documents. Here is how the most common methods compare.
| Method | Encrypted? | How It Works | Common EDI Use |
|---|---|---|---|
| HTTPS | Yes (TLS) | Web request and response over TLS, usually port 443 | Web services, APIs, web EDI portals |
| AS2 | Yes (message encryption and signing; can also use TLS) | Sends documents over HTTP or HTTPS with digital signatures and receipts (MDNs) | Direct connections required by many large retailers |
| SFTP | Yes (SSH) | File transfer over SSH, usually port 22 | Batch file exchange with 3PLs, manufacturers and VANs |
| FTPS | Yes (TLS) | FTP with TLS encryption added | Older systems that need FTP with encryption |
| FTP | No | Plain file transfer | Not recommended for business documents |
| HTTP | No | Plain web request and response | Not recommended for business documents |
An AS2 receipt (MDN) confirms a message was delivered, not that your partner accepted the document. Functional acknowledgments, such as the EDI 997, confirm that the partner's system received and processed it.
HTTPS has two main trade-offs, and both are usually manageable:
The right method usually depends on your trading partners. Many large retailers require AS2, 3PLs often use SFTP, and API-based integrations typically use HTTPS. Whatever the method, choose an encrypted one.
Setting up and maintaining multiple connection methods, certificates and partner requirements takes time. With BOLD VAN, our team configures your connection methods and onboards your trading partners for you, with new trading partners typically live within about a business day.
2026 Free Mapping Event
New to EDI or moving from another provider? Through Dec. 31, 2026, we build and maintain the maps for the trading partners you move to BOLD Integration, at no mapping cost.
Tell us how your trading partners connect, and we will handle the setup. Call (844) 265-3777 or email info@boldvan.com.
Talk to an EDI ExpertHTTPS stands for HyperText Transfer Protocol Secure. It is the encrypted version of HTTP.
Yes. HTTPS encrypts data in transit with TLS and verifies the server's identity, making it a secure way to exchange EDI documents over the internet. Stored data should also be protected with encryption at rest.
HTTPS is a general-purpose secure web protocol. AS2 is a standard built specifically for exchanging business documents; it runs over HTTP or HTTPS and adds message-level encryption, digital signatures and delivery receipts (MDNs).
Both are secure when configured correctly. HTTPS encrypts with TLS and is common for web services and APIs. SFTP encrypts with SSH and is common for batch file transfers. The best choice usually depends on what your trading partner supports.
No. Plain FTP sends data unencrypted. For EDI, use an encrypted method such as SFTP, FTPS, AS2 or HTTPS.
HTTPS uses port 443 by default. Plain HTTP uses port 80.
No. HTTPS protects data while it travels. Stored data needs separate encryption at rest. BOLD VAN encrypts documents both in transit and at rest.
TLS is the successor to SSL. Modern HTTPS uses TLS, though the older term "SSL certificate" is still widely used.
Key Facts
HTTPS (HyperText Transfer Protocol Secure) is HTTP combined with TLS. It encrypts data in transit, verifies the server with a certificate and uses port 443 by default. Plain HTTP (port 80) and plain FTP are not encrypted and are not recommended for EDI.
In EDI, HTTPS is one of several encrypted connection methods, along with AS2 and SFTP. AS2 runs over HTTP or HTTPS and adds signatures and delivery receipts; an AS2 receipt confirms delivery, not acceptance. BOLD VAN supports HTTPS, AS2, SFTP and FTPS and encrypts documents in transit and at rest on SOC 2 Type II audited infrastructure.
