On this page
- How MDN works
- Machine-readable MDN fields (RFC 4130)
- MDN structure
- MDN request headers (RFC 4130)
- Synchronous vs asynchronous MDN
- Platform constraints on MDN mode
- Non-repudiation of receipt (NRR)
- Important caveat
- Retailer compliance requirements
- Walmart (as-of 2026)
- Amazon (as-of 2026)
- Target (as-of 2026)
- Security considerations
- Common implementation failures
- MDN timeout / not received
- MIC mismatch
- Signature verification failure
- Inbound failure codes
- Outbound failure codes
- Key terms
- Benchmarks (as-of 2026-11-02)
- What practitioners report
Message Disposition Notification (MDN)
Message Disposition Notification (MDN)
A Message Disposition Notification (MDN) is a cryptographic receipt returned by the receiver of an AS2 (Applicability Statement 2) message to confirm successful receipt and processing of that message. It is the AS2 protocol's defining mechanism for establishing non-repudiation of receipt (NRR) — proof that a specific EDI (Electronic Data Interchange) document arrived, was decrypted correctly, and had its signature verified, which neither party can credibly deny.
How MDN works
According to Stedi's AS2 platform documentation, the MDN serves three purposes: acknowledgment (confirms message arrival), security (confirms successful decryption and signature verification), and non-repudiation (provides evidence for disputes or audits). (Source: Web — Message Disposition Notification MDN 2026-11-02)
The Sysax reference on MDN proof-of-delivery describes the MDN as having two parts — a human-readable section and a machine-readable section — with the machine-readable part carrying the legal weight in disputes.
Machine-readable MDN fields (RFC 4130)
The Sysax source specifies three key fields in the machine-readable MDN:
| Field | What it carries |
|---|---|
Original-Message-ID | Links the receipt back to the original message |
Received-Content-MIC | Cryptographic hash of the received content |
Disposition | The processing outcome: see values below |
Disposition field values (per Sysax, sourcing RFC 4130):
processed— success; document received and passed signature/decryption checksprocessed/error— received but with an error (e.g.,decryption-failed,authentication-failed)failed/failure— the station could not evaluate the message at all
MDN structure
RFC 4130 specifies the signed MDN is structured as multipart/signed, with two parts:
- Part 1: The MDN itself, including MIME headers
- Part 2:
application/pkcs7-signature
MDN request headers (RFC 4130)
Three AS2 HTTP headers control MDN behaviour:
| Header | Purpose |
|---|---|
Disposition-notification-to | Requests that the receiver return an MDN |
Disposition-notification-options | Specifies signing protocol and MIC algorithm (e.g., signed-receipt-protocol=optional,pkcs7-signature and signed-receipt-micalg=optional,sha1,md5) |
Receipt-Delivery-Option | URL for asynchronous MDN delivery; absent = synchronous (per RFC 4130, if absent the MDN must be synchronous) |
(Source: Web — Message Disposition Notification MDN 2026-11-02)
Synchronous vs asynchronous MDN
| Mode | How it works | When to use |
|---|---|---|
| Synchronous | MDN returned within the same HTTP/S exchange as the original POST | Low-latency needs; required when Receipt-Delivery-Option is absent |
| Asynchronous | Receiver first sends bare HTTP ACK on the original connection; sends signed MDN in a separate HTTP POST to the sender's endpoint later | Large files, high-latency partners; delays can be up to one hour |
For asynchronous MDN, the sender must operate a reachable endpoint (the URL in Receipt-Delivery-Option) and track messages awaiting receipts. (Source: Web — Message Disposition Notification MDN 2026-11-02, sourcing Sysax)
Platform constraints on MDN mode
Stedi's AS2 implementation accepts only synchronous MDNs for outbound messages — trading partners must return MDNs synchronously. (Stedi documentation) VS Orderful also supports only synchronous MDNs — trading partners configured for async must switch to synchronous. (Orderful support) This is a platform constraint rather than a protocol conflict: both platforms have independently restricted themselves to sync-only, meaning suppliers using these platforms cannot use async MDN even if a retailer's configuration requests it.
Non-repudiation of receipt (NRR)
RFC 4130 specifies that NRR is most reliably established when both the original message and the MDN are signed. The verification loop:
- Sender signs original message with its private key
- Receiver signs the MDN with its private key
- Sender verifies the MDN signature using the receiver's public key
- Sender confirms the MIC value in the MDN matches the stored MIC from the original message
- Because only the partner's private key could produce the signature, the partner cannot later deny having received the exchange
The Sysax source describes this as "mutual non-repudiation" when both directions are signed.
Evidence value of a signed MDN (per Sysax): supports disputes including claims of non-receipt, corrupted file delivery, late delivery, and duplicate orders. The MIC, signature, and timestamps collectively form the record.
Retention requirement (per Sysax): signed MDNs must be kept with their original messages, indexed by Message-ID and document number, for the period set by finance and legal teams. "A receipt you cannot find is a receipt you do not have."
Important caveat
A positive MDN (processed) does not confirm that the EDI document was parsed or acted upon at the business level. That confirmation requires a separate functional acknowledgment — typically the X12 997 (Functional Acknowledgement) — which confirms the EDI content itself was accepted by the trading partner's application. (Source: Web — Message Disposition Notification MDN 2026-11-02, sourcing Sysax)
Retailer compliance requirements
All retailer-specific requirements below are sourced from the Aayu Technologies vendor blog (aayutechnologies.com), not from official Walmart Retail Link, Amazon Vendor Central, or Target Partners Online documentation. Those portals require login. Requirements should be verified against the official supplier portals before acting on them.
Walmart (as-of 2026)
Per Aayu Technologies (2026 EDI compliance article): Walmart requires that every AS2 message generates a signed MDN in return. A missing MDN is treated as non-delivery. Walmart requires SHA-256 signed certificates with a minimum 2048-bit key length; certificate expiration breaks the AS2 connection immediately. Suppliers processing more than 5,500 invoices per year must connect via AS2, and must pass a formal test sequence with explicit sign-off before any live purchase order is processed.
OTIF (On-Time In-Full) violations caused by MDN failures and resulting non-delivery events can trigger chargebacks of approximately 3% of cost of goods (as-of 2026).
The SHA-256/2048-bit requirements in the Aayu Technologies article [https://aayutechnologies.com/blog/master-walmart-as2-and-amazon-mandates/] do not match the original RFC 4130 specification, which recommended SHA-1 as the MIC algorithm when the RFC was published in 2005 [RFC 4130]. This is not a logical contradiction — industry practice evolved to SHA-256 — but an implementation following the raw RFC would be non-compliant with Walmart's current requirements.
Amazon (as-of 2026)
Per Aayu Technologies (2026): Amazon requires an EDI X12 997 Functional Acknowledgement for every EDI transaction. Transport-level AS2 MDN requirements for Amazon Vendor Central are not publicly documented; the specifics appear to be behind the Amazon Vendor Central portal login. Whether Amazon requires signed MDN receipts specifically was not confirmed by a public source.
Target (as-of 2026)
Per Aayu Technologies (2026): Target expects full compliance from the first live transaction with no grace period. Target's Partners Online portal tracks every EDI document (855, 856, 810) and scores fill rate, on-time delivery, and ASN accuracy; penalties for ASN violations may scale per carton. No MDN-specific signing or certificate requirements for Target were found in public sources.
Security considerations
The IBM AS2 overview describes AS2's use of digital certificates for mutual authentication and encryption. Both signing and encryption use certificate-based public-key cryptography. The sender requests a signed MDN by including Disposition-notification-options with the signing protocol and MIC algorithm; after processing, the recipient signs the MDN with its private key; the sender verifies the signature with the recipient's public key. (Source: Web — Message Disposition Notification MDN 2026-11-02)
Important: An HTTP 200 OK response from the trading partner confirms receipt at the HTTP layer only. It does not confirm successful decryption, signature verification, or EDI-level acceptance. Only a positive MDN Disposition field value of processed provides that confirmation. (Source: Aayu Technologies troubleshooting blog)
Common implementation failures
MDN timeout / not received
Per Orderful support documentation, three categories:
- Partner AS2 server is unresponsive or has connectivity problems
- Partner AS2 server is misconfigured (e.g., async when sync is required)
- Internal routing or processing fault on the partner's side prevented MDN generation
The Orderful source notes: sudden MDN failures on a previously stable connection are most commonly caused by a recent change on the partner's AS2 server — certificate renewal, software update, or configuration change.
Before resending after a timeout: confirm whether the receiver actually processed the message, since the receiver may have already processed it and a retransmission could cause duplicate EDI documents. (Source: Aayu Technologies troubleshooting blog)
MIC mismatch
error: "Received MIC does not match the expected MIC" — caused by (per Aayu Technologies):
- Data corruption in transit
- Mismatched hash algorithm string formats between parties (e.g.,
"sha-256"vs"sha256") - Compression or encoding differences
Signature verification failure
Caused by (per EDI Bull blog, 2025-03):
- Expired or invalid certificate
- Wrong partner certificate mapped in the AS2 configuration
- Signature algorithm mismatch between parties
Inbound failure codes
| Symptom | Likely cause |
|---|---|
| HTTP 422 | AS2-From or AS2-To identifiers don't match the trading partner config |
| Decryption failure | Wrong or outdated encryption certificate |
| Signature verification failure | Untrusted certificate chain, or Content-Transfer-Encoding mismatch causing a digest-at-rest vs digest-in-transit discrepancy |
Outbound failure codes
| HTTP response | Meaning |
|---|---|
| 301/302/307 | Incorrect partner URL (redirect) |
| 401/403 | Authentication failure or firewall block |
| 413 | Payload exceeds receiver's size limit |
| 400/422 | Malformed request or invalid identifiers |
| 500–504 | Receiver-side outage or gateway timeout |
(Source: Aayu Technologies troubleshooting blog)
Key terms
| Term | Meaning |
|---|---|
| MDN | Message Disposition Notification — the AS2 cryptographic receipt |
| NRR | Non-Repudiation of Receipt — legal evidence neither party can deny the exchange |
| MIC | Message Integrity Check — SHA-256 hash of the transmitted content |
| Sync MDN | MDN returned within the same HTTP/S connection as the original POST |
| Async MDN | MDN sent in a separate HTTP/S connection to a return URL specified by the sender |
processed | MDN Disposition value indicating successful receipt and verification |
processed/error | MDN Disposition value indicating receipt with a specific error (decryption-failed, authentication-failed) |
failed/failure | MDN Disposition value indicating the station could not evaluate the message |
| X12 997 | Functional Acknowledgement — business-level EDI acceptance, separate from MDN's transport-level confirmation |
| OTIF | On-Time In-Full — Walmart's supplier performance metric; MDN failures contribute to OTIF violations |
Benchmarks (as-of 2026-11-02)
- Walmart OTIF chargeback rate for non-compliance: ~3% of cost of goods (as-of 2026, per Aayu Technologies vendor blog)
- Walmart AS2 threshold: 5,500+ invoices/year (as-of 2026, per Aayu Technologies vendor blog)
- Async MDN delivery delay: can be up to 1 hour (per Aayu Technologies blog — no date given for original data)
What practitioners report
Per Orderful support documentation: the most common cause of a sudden MDN failure on a previously working connection is a recent change on the partner side — especially certificate renewal. Recommends checking for partner-side changes before escalating.
Per Aayu Technologies troubleshooting blog: MIC mismatch errors caused by hash algorithm string format differences (sha-256 vs sha256) are a frequent "mystery error" where both parties believe they are using the same algorithm but the strings don't match at the protocol level.