AS2
Direct exchange between partners.
AS2 transports business documents over HTTP or HTTPS. It can combine signing, encryption and MDN acknowledgements, depending on the interchange agreement.
What needs to be defined
AS2 identifiers, receiving URL, certificates, algorithms and MDN response mode.
An MDN reports the outcome of message processing at the AS2 level; on its own, it does not prove business acceptance of the order or invoice.
AS2 specification · RFC 4130 ↗AS4
Structured, secure messaging.
AS4 is an ebMS 3.0 profile for B2B messaging. It uses SOAP and security and receipt mechanisms, and is used notably in the Peppol ecosystem.
What needs to be defined
Exchange profile, identifiers, certificates, security settings and receipt rules.
The selected profile and its interoperability requirements matter just as much as the protocol name.
AS4 specification · OASIS ↗SFTP
File transfer over SSH.
SFTP lets you upload and retrieve files over an SSH connection. It is a useful interface when business software works with import and export directories.
What needs to be defined
SSH keys, host verification, permissions, directories, naming conventions and polling frequency.
Business monitoring, duplicate detection and recovery rules need to be designed on top of the file transfer layer.
API / HTTPS
Exchanges at the pace of your applications.
An API exposes operations your applications can call to send a document or check a status. Its contract specifies the expected data, responses and error handling.
What needs to be defined
Authentication, schemas, versioning, rate limits, idempotency and any webhooks.
An API does not replace business rules: mapping and checks remain essential.
OFTP2
An industrial exchange protocol.
Originating in the Odette ecosystem, OFTP2 enables file transfers between partners. It includes security, signing and acknowledgement features.
What needs to be defined
Odette identifiers, certificates, session settings and end-to-end confirmations.
OFTP2 is a protocol in its own right; it is not a variant of conventional FTP.
OFTP2 specification · RFC 5024 ↗X.400
Connect to existing networks.
X.400 is a family of messaging standards used in some EDI environments. It relies on addressing and transfer services specific to that ecosystem.
What needs to be defined
O/R address, operator or gateway, routing and available notifications.
The connection depends on the network and the services of the operator involved. We assess feasibility in your environment.
X.400 recommendations · ITU ↗From transport to content
What is inside
the message?
Orders, despatch advice and invoices: each document has its own structure and rules.
Understand EDI formats