EDI
API DocsTerminal
NEW!
Programmatically translate EDI to JSON with the EDI Core REST API
Get started in minutes →
Transaction Set
in
X12 Release 008020

993 Secured Receipt or Acknowledgment

Functional Group NR

X12C Communications and Controls Subcommittee

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.

Heading

Sequence
Segment
Name
Max use
0100
Transaction Set HeaderMandatory
Max 1
To indicate the start of a transaction set and to assign a control number
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.
0200
Functional Group Response HeaderMandatory
Max 1
To start acknowledgment of a functional group
0300
Transaction Set Response Header
Max 1
To start acknowledgment of a single transaction set
0400
Security Protocol Error
Max 1
To report security protocol errors in a security structure
A single 993 can report only security protocol or assurance protocol errors; therefore only one SPE or APE segment can occur per transaction.
At least one occurrence of the SPE, APE, or S4A loop must be used.
0500
Assurance Protocol Error
Max 1
To report assurance protocol errors in a security structure
A single 993 can report only security protocol or assurance protocol errors; therefore only one SPE or APE segment can occur per transaction.
At least one occurrence of the SPE, APE, or S4A loop must be used.
S4A Loop
Repeat 2
0600
Assurance Header Level 2
Max 1
To allow for multiple assurances at the ST/SE level
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.
At least one occurrence of the SPE, APE, or S4A loop must be used.
0700
Security Value
Max 1
To provide the encoded output of a cryptographic algorithm
0800
Transaction Set TrailerMandatory
Max 1
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference and Mapping Guides are provided for marketing purposes and are free of charge. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.
Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference and Mapping Guides are provided for marketing purposes and are free of charge. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.