Skip to main content
All CollectionsX12 EDITransaction Sets900-999
X12 - 993 - Secured Receipt or Acknowledgement
X12 - 993 - Secured Receipt or Acknowledgement
Micah A. Parker avatar
Written by Micah A. Parker
Updated yesterday

Product: X12 EDI

Transaction: 993


993 - Secured Receipt or Acknowledgment
FUNCTIONAL GROUP=NR

This X12 Transaction Set contains the format and establishes the data contents of the Secured Receipt or Acknowledgment Transaction Set (993) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set provides three distinct security services: the 993 provides security protocol error reporting, non-repudiation of receipt for X12.58 authenticated transaction sets or functional groups, and transmission of authentication independent of the document for which the authentication is rendered. When the 993 is used to pass a dis-embodied signature (non-repudiation of origin), both the transaction set and the 993 with the assurance for the transaction set may be transmitted completely independent of each other. A 993 may be generated as a 'trusted receipt' for a 993 that contained a dis-embodied signature.


SCHEMA


ST

Segment

Name

Required

ST

Transaction Set Header

M

AK1

Functional Group Response Header

M

AK2

Transaction Set Response Header

O

SPE

Security Protocol Error

O

APE

Assurance Protocol Error

O

S4A

Segment

Name

Required

S4A

Assurance Header Level 2

O

SE

Segment

Name

Required

SE

Transaction Set Trailer

M


COMMENTS


Notes

1/0100

A 993 used to report a security protocol or assurance protocol error shall not be acknowledged, thereby preventing an endless cycle of acknowledgments of acknowledgments.

1/0400

A single 993 can report only security protocol or assurance protocol errors; therefore only one SPE or APE segment can occur per transaction.

1/0400

At least one occurrence of the SPE, APE, or S4A loop must be used.

1/0500

A single 993 can report only security protocol or assurance protocol errors; therefore only one SPE or APE segment can occur per transaction.

1/0500

At least one occurrence of the SPE, APE, or S4A loop must be used.

1/0600

When two iterations of the S4A loop are used, the first iteration shall contain the assurance (digital signature) and the second iteration shall be used for a trusted time stamp.

1/0600

At least one occurrence of the SPE, APE, or S4A loop must be used.

rev 11/19/2024

Did this answer your question?