On this page
- What it means and why it matters
- Technical implementation
- AS2 MDN — non-repudiation of receipt in EDI
- Algorithm note (as-of 2026-11-08)
- JSCAPE/IBM practitioner framing
- Critical distinction: email MDN vs. AS2 MDN
- AS4 and EU eDelivery AS4 2.0
- Legal framework — eIDAS and qualified electronic signatures
- eIDAS 2.0 — Regulation EU 2024/1183 (as-of 2026-11-08)
- Challenges and limitations
- What practitioners report
- Key terms
Non-Repudiation
Non-Repudiation
Non-repudiation is the cryptographic and legal guarantee that a party cannot credibly deny having performed a specific action — sending a message, receiving a document, or approving a transaction. In ecommerce and supply chain EDI it is the evidential foundation for purchase order acknowledgements, invoice authentication, and delivery proofs: when a trading partner claims they never received a shipment notice or never sent a price-change order, non-repudiation evidence settles the dispute.
What it means and why it matters
NIST SP 800-60 defines non-repudiation as "assurance that the sender is provided with proof of delivery and the recipient is provided with proof of the sender's identity, so neither can later deny having processed the information" (csrc.nist.gov, accessed 2026-11). NIST SP 800-63-4 narrows this to the commerce context: "the capability to protect against a person falsely denying having performed a particular transaction" (csrc.nist.gov, accessed 2026-11).
The concept originated as a legal idea and is now fundamental to both information security and B2B commerce. TechTarget notes that non-repudiation is distinct from authentication: authentication confirms who sent something; non-repudiation makes it impossible to later deny that it was sent (techtarget.com). ISMS.online reinforces the distinction: authentication alone does not stop a party from later denying an action — non-repudiation adds cryptographic binding to identity so a later denial is not legally credible (isms.online).
In EDI supply chains, non-repudiation has two operational pillars (Professor Messer, CompTIA SY0-701, YouTube 2023-11):
- Proof of origin — the sender cannot deny having dispatched a document
- Proof of delivery — the receiver cannot deny having received it
Technical implementation
ISMS.online and Portnox identify the core technical mechanisms:
| Mechanism | Role |
|---|---|
| Digital signatures (asymmetric cryptography) | Private key signs; public key verifies; only the key-holder can have produced the signature |
| PKI / X.509 certificates | Certificate Authority binds a public key to a verified identity; revocation enables detection of compromised keys |
| Cryptographic hashing | Tamper-detection; a single changed bit invalidates the hash |
| Trusted timestamping (RFC 3161) | A Time Stamping Authority (TSA) binds a document hash to the current time and returns a signed timestamp token; the document content is never transmitted — only its hash (idura.eu) |
| Signed receipts/confirmations | Both parties retain a mutually verifiable acknowledgement |
TechTarget identifies a critical architectural constraint: Message Authentication Codes (MACs) provide integrity and authentication but NOT non-repudiation, because both parties share the same secret key so either could have created the MAC. Asymmetric key cryptography (digital signatures) is therefore required (techtarget.com).
AS2 MDN — non-repudiation of receipt in EDI
Message Disposition Notification (MDN) is the primary mechanism for non-repudiation of receipt (NRR) in AS2-based EDI supply chains.
RFC 4130 (AS2, IETF 2005) defines NRR as "a legal event" that occurs when the original sender has verified the signed MDN returned by the receiver (Section 1.2). The RFC explicitly frames NRR as "not a technical message" but a business or legal requirement.
The NRR sequence (RFC 4130):
- Sender signs the EDI payload with its private key (non-repudiation of origin)
- Receiver processes the message and returns a signed MDN containing:
- The original Message-ID
- A Received-content-MIC (SHA-256+ hash of the received payload)
- The receiver's digital signature over the MDN
- Sender verifies the MDN signature against the receiver's public key AND confirms the MIC matches the digest of its original message
- The verified, retained signed MDN constitutes the NRR evidence
RFC 4130 Section 9.1: "To satisfy strict NRR evidence, authentication and integrity MUST be provided by some mechanism." If the original message is not signed, an alternative authentication path (client SSL, IPsec, HTTP authentication over SSL) must accompany the receipt request.
Algorithm note (as-of 2026-11-08)
RFC 4130 specifies SHA-1 and MD5 as supported hash algorithms. SHA-1 is now considered cryptographically weak. Azure Logic Apps (Microsoft) supports SHA1, MD5, SHA2-256, SHA2-384, and SHA2-512 for AS2 MDN signing (learn.microsoft.com). Modern implementations should use SHA-256 or stronger.
RFC 4130 (2005) specifies SHA-1 as the recommended algorithm. Walmart, Amazon, and major retailers now mandate SHA-256 or stronger in their AS2 trading partner agreements. Check specific retailer EDI specifications for current algorithm requirements.
JSCAPE/IBM practitioner framing
JSCAPE (vendor) documents that NRR in EDI is contractual as well as technical: "Whether digital signatures are required on the MDN is part of your trading partner agreement and is typically mandatory for high-value B2B transactions." IBM AS2 documentation confirms that the goal of NRR is to establish the sender and receiver, the contents of the transmitted file, and that the contents were not altered in transit (ibm.com).
SEEBURGER notes that certificate management (renewal, GLN routing, firewall port management) is operationally intensive at scale — this is a practical challenge for supply chain teams managing hundreds of trading partner connections (seeburger.com).
Critical distinction: email MDN vs. AS2 MDN
RFC 3798 (email MDN, IETF 2006) explicitly states: "MDNs do not provide non-repudiation with proof of delivery" (Section 6.3). Email MDNs can be forged "as easily as ordinary Internet electronic mail," recipients can bypass the mechanism, and a "displayed" disposition only means the message was shown to someone — not that it was read or understood.
RFC 4130 (AS2 MDN) describes the signed MDN as the mechanism that achieves NRR — when implemented with S/MIME-signed receipts and PKI-backed certificates.
These are not contradictory — they describe fundamentally different implementations. Email MDN (RFC 3798): unsigned, forgeable, no NRR. AS2 MDN (RFC 4130): signed with S/MIME, verifiable against PKI, provides NRR when configured correctly.
AS4 and EU eDelivery AS4 2.0
AS4 (the successor protocol to AS2 for B2B/G2G messaging) provides NRR through XML Digital Signatures and signed receipt signals. The EU eDelivery AS4 2.0 specification (ec.europa.eu, published 2024-12-05) states: "The eDelivery AS4 profile provides Non Repudiation of Origin and Receipt at the level of Message Exchange."
EU eDelivery AS4 2.0 key NRR requirements (as-of 2024-12-05):
- Signing uses Ed25519 (eddsa-ed25519) with SHA-256 digests — a significant algorithm upgrade from earlier AS4/AS2 implementations
- AES-128-GCM encrypts payloads with X25519 key agreement and HKDF
- TLS 1.3 recommended (TLS 1.2 minimum)
- The signed receipt signal must be sent synchronously (
PMode[].Security.SendReceipt.NonRepudiation = true) - Parties must retain exchanged messages and receipts for as long as disputes may arise; retention period should be specified in formal policy
IBM B2B Advanced Communications documents that AS4 NRR implementation stores raw inbound and outbound requests, the ebbpsig:NonRepudiation-Information element from the signed receipt, and audit log entries recording certificate, signature hash algorithm, subject ID, and source/destination IP (ibm.com).
Legal framework — eIDAS and qualified electronic signatures
Under EU eIDAS (Regulation 910/2014, Article 25), a Qualified Electronic Signature (QES) has the same legal effect as a handwritten signature across all EU member states and carries the highest evidentiary value for disputes (blueink.com).
eIDAS 2.0 — Regulation EU 2024/1183 (as-of 2026-11-08)
eIDAS 2 (Regulation EU 2024/1183, published May 2024) is in active rollout. Implementation provisions run through 2027–2028. Status below is current as of 2026-11.
Certyneo (vendor) reports that under eIDAS 2, when a QES is used "the burden of proof is reversed": the party contesting a QES-signed document must prove alteration, while the party invoking the document need not prove its validity (certyneo.com, 2025). This strengthens non-repudiation at the legal level, not merely the cryptographic level.
Certyneo notes both that eIDAS 2 "reverses the burden of proof" for QES documents AND that eIDAS 2 "extends no new direct obligations to private B2B/B2C transactions before 2026 deadlines." This apparent tension reflects two separate truths: eIDAS 2 strengthens the evidence presumption for QES (courts must accept them as equivalent to handwritten signatures) without mandating that businesses use QES in their private contracts.
New eIDAS 2 provisions relevant to ecommerce non-repudiation (certyneo.com, 2025):
- Reversed burden of proof for Qualified Trust Service Providers (QTSPs) under Article 13
- Two new qualified trust service categories: qualified electronic archiving services; qualified remote signature creation device management (enabling QES without a physical smart card)
- EU Digital Identity (EUDI) Wallet: each EU Member State must provide a wallet by November 2026 (as-of 2026-11-08); large online platforms (>45M monthly EU users) must accept it for authentication by 2027
- QTSPs must comply with NIS2 (Directive 2022/2555), including security incident notification within 24 hours
Signatures issued under eIDAS 1 retain their legal validity; there is no obligation to re-sign existing documents (certyneo.com, 2025).
Challenges and limitations
TechTarget identifies a gap between cryptographic and legal proof: "current legal frameworks do not consider whether the signer was coerced or deceived" — a valid signature does not prove consent. Malware stealing or forging a private key could invalidate NRR evidence (techtarget.com).
Sysax documents the "gap between technical and legal proof": a technically valid signature establishes cryptographic NRR but may not by itself satisfy a court's evidentiary standards; evidence requires assembling logs, hashes, signatures, and receipts into a coherent narrative, and "unsynchronized clocks poison evidence" (sysax.com).
ISMS.online lists operational challenges: cryptographic and key management complexity; integration disruption; substantial upfront and ongoing costs; private key compromise or implementation flaws can undermine the entire framework; quantum computing could threaten the asymmetric cryptography that digital signatures rely on (isms.online).
What practitioners report
No Reddit findings captured (MCP tools unavailable in this execution environment — consistent gap in prior runs). No YouTube transcripts captured (Apify MCP unavailable). The JSCAPE (vendor) tutorial shows practitioners treating NRR as a standard AS2 configuration item rather than a legal concept, which glosses over the distinction between contractual NRR (B2B trading partner agreement) and statutory NRR (eIDAS QES).
Key terms
| Term | Meaning |
|---|---|
| Non-Repudiation of Origin (NRO) | Proof that a specific sender dispatched a message |
| Non-Repudiation of Receipt (NRR) | Proof that a specific receiver accepted a message |
| Signed MDN | A Message Disposition Notification bearing the receiver's digital signature; the AS2/AS4 mechanism for NRR |
| MIC (Message Integrity Code) | Hash of the transmitted content included in a signed MDN; verifies content integrity |
| Qualified Electronic Signature (QES) | eIDAS-defined highest-trust e-signature; legally equivalent to a handwritten signature across EU |
| TSA (Time Stamping Authority) | A trusted third party that binds a document hash to a point in time per RFC 3161 |
| PKI | Public Key Infrastructure; the CA-managed system that binds public keys to verified identities |
| AU-10 | NIST SP 800-53 control covering non-repudiation requirements for US federal systems |