Communication protocols
Connect each partner the way it is set up to connect
Some partners require AS2 with signed receipts, banks often use SFTP, European partners may use AS4, and older connections still run over FTP or email. ECOM connects each partner over the protocol it requires, hosting the connection as a server or connecting to the partner's server as a client, all on one monitored platform.
At a glance
- Server and client roles
- Certificates and keys
- Receipts and retries
What is a B2B communication protocol?
A B2B communication protocol is the method two companies use to move documents between their systems, defining how the connection is opened, how files are secured and how receipt is confirmed. The protocol is separate from the document standard, so an X12 file can travel over AS2, SFTP or HTTPS.
Outcomes
What you can expect
Meet each partner's requirement
Partners keep the protocol they mandate, while your team manages every connection in one place.
Security per connection
Encryption, certificates, keys and signed receipts are configured to each protocol and partner policy.
Visibility of every transfer
Successful, delayed and failed transfers are monitored, with alerts before a missing file becomes a missed shipment.
Approach
How ECOM delivers it
-
Server and client roles
For SFTP, FTP and FTPS, ECOM can host the connection for partners to reach, or connect out to the partner's server.
-
Certificates and keys
Certificates and SSH keys are managed for each partner, with renewals planned before they expire.
-
Receipts and retries
Signed receipts (MDNs) are reconciled where the protocol supports them, and failed transfers are retried and alerted.
Applicability Statement protocols
AS1, AS2, AS3 and AS4
The Applicability Statement family of protocols for secure, receipted business document exchange.
-
AS1
Secure document exchange over email (SMTP) with encryption, signatures and receipts.
AS1 in detail -
AS2
Secure, real-time exchange over HTTP or HTTPS with signed receipts, widely required by retailers.
AS2 in detail -
AS3
Secure exchange over FTP, adding encryption, signatures and receipts to file-based transfers.
AS3 in detail -
AS4
Web-services exchange based on ebMS, used in European and government networks for receipted messages.
AS4 in detail
File transfer
SFTP, FTP and FTPS, as server and client
File-based connections, hosted by ECOM for partners or connecting out to partners' servers.
-
SFTP
File transfer over SSH, common for banks, logistics providers and partner drop-offs, as server or client.
SFTP in detail -
FTPS
FTP secured with TLS, for partners that require certificate-based encryption, as server or client.
FTPS in detail -
FTP
Plain FTP for legacy partners that have not yet moved to a secure protocol, as server or client.
FTP in detail
Web and email
HTTP/HTTPS and SMTP
-
HTTP and HTTPS
Document exchange with web endpoints and APIs, with HTTPS encryption for data in transit.
HTTP and HTTPS in detail -
SMTP
Email-based exchange for partners that send or receive documents as messages and attachments.
SMTP in detail -
SOAP and web services
Service-based exchange with partners and applications that publish or consume SOAP web services.
SOAP and web services in detail -
REST APIs
Calls to and from REST APIs. How each payload is handled is confirmed during scoping.
REST APIs in detail -
WebDAV
Document exchange with partners that publish a WebDAV folder over HTTP or HTTPS.
WebDAV in detail
B2B exchange frameworks
OFTP, RosettaNet RNIF, ebXML and Zengin
Frameworks used by specific industries and regions. Protocol versions and configuration are confirmed during scoping.
-
OFTP and OFTP2
The Odette file transfer protocol used across the European automotive supply chain, including the secure OFTP2 version.
OFTP and OFTP2 in detail -
RosettaNet RNIF
The RosettaNet Implementation Framework that packages, signs and acknowledges Partner Interface Process messages.
RosettaNet RNIF in detail -
ebXML
Internet B2B message packaging and exchange based on ebXML.
ebXML in detail -
Zengin TCP/IP
The Zengin TCP/IP communication option used for Japanese banking exchanges.
Zengin TCP/IP in detail
Scenarios
Common scenarios
Retailer AS2 requirement
A supplier must connect to a new retail customer over AS2 with signed receipts before its first order.
Bank file exchange
Payment and statement files move to and from banks over SFTP with key-based authentication.
Retiring plain FTP
Legacy FTP connections are replaced by SFTP or FTPS partner by partner, without disrupting shipments.
Frequently asked questions
Can ECOM host an SFTP server for our partners and also connect to theirs?
Yes. For SFTP, FTP and FTPS, ECOM can act as the server that partners connect to, or as the client that connects to each partner's server.
Which protocol should we use with a new partner?
Use the protocol the partner requires. Where there is a choice, AS2 or SFTP with encryption are common, and ECOM recommends the option that fits the partner's capabilities.
Do you still support plain FTP?
Yes, for partners that require it, while recommending a move to SFTP or FTPS when the partner is ready, because plain FTP does not encrypt data.
Set up your partner connections
Tell us which partners and protocols you need. ECOM confirms the connection setup, certificates and testing plan.