Supply chain collaborationAS2 Meet embedded SpicY™ AI

SPICE™ Glossary / AS2

AS2

AS2 (Applicability Statement 2) is a protocol for sending EDI and other business files directly and securely over the internet, using encryption, digital signatures and signed delivery receipts.

AS2 moves documents over HTTP or HTTPS between two parties’ AS2 software. Before a document leaves, it is signed with the sender’s certificate and encrypted with the receiver’s, so only the intended trading partner can read it and the trading partner can verify who sent it. The receiver returns a message disposition notification (MDN), a signed receipt confirming the file arrived intact.

Because it connects trading partners directly, AS2 avoids the per-document fees of an EDI VAN and delivers in near real time. Many large retailers and manufacturers require it for EDI. Setup involves exchanging AS2 identifiers, endpoint URLs and certificates, then testing the connection before production.

The common failures are operational: an expired or replaced certificate, a changed URL or firewall rule, or an MDN that never comes back. Any of these can stop orders or invoices quietly until someone notices. An MDN confirms delivery of the file only; the next check is the functional acknowledgment, and the business review comes after that.

How SPICE™ handles it

SPICE™ supports AS2 connections with trading partners and enterprise systems, alongside SFTP, APIs and EDI. See security and integrations. When an AS2 connection fails or a certificate expires, the team behind SPICE Connect™ diagnoses it with the trading partner and coordinates the fix, so your team does not have to act as the go-between.

FAQ

Frequently asked questions

What is an MDN in AS2?

An MDN (message disposition notification) is the receipt an AS2 system sends back after receiving a file. A signed MDN proves the file arrived and was not altered in transit. It does not confirm that the content of the document is correct.

Is AS2 better than SFTP?

Neither is better in every case. AS2 builds signing, encryption and receipts into the protocol and delivers in near real time. SFTP is simpler and common for scheduled batch exchanges. Many companies use both, depending on what each trading partner requires.