Code indicating the version/release of the ASC X12 standard that is being used for this specific security structure. The version/release identified for this segment also applies to any corresponding trailer or security value segment. This version/release is independent of any other version/release identified in another security segment at the transaction set or functional group level. This version/release is independent of the version/release identified at the interchange or functional group level

Code specifying the business purpose of the appended assurance to an existing secured-entity (whether functional group or transaction set); the codes represent the intention of the business or application that has control over the assurance originator

Code specifying the bounds of the text, whether contiguous or not, over which the computation of the Assurance Token is computed using the defined methodology of computation and any relevant Assurance Token parameters The "body" is defined as a transaction set, beginning with the first byte of the segment immediately following the ST segment terminator and including all segments up to but not including the "S" in the first SVA segment; DO NOT include any S4A segments The "body" can also be defined as a functional group, beginning with the first byte of the segment immediately following the GS segment terminator and including all transaction sets up to but not including the "S" in the first SVA segment at the functional group level; DO NOT include any S3A segments "This Assurance" is defined as from the "S" in S3A or S4A up to and including the segment terminator of that segment "Previous Assurance(s)" is defined as including the entire S3A or S4A segment and the entire corresponding SVA segment that is associated with the S3A or S4A at the same level

Unique designation (identity) of the cryptographic process that performs the stated assurance on data to be interchanged Note: X9 has a required minimum length of 4 characters for a security originator; no mechanism, or registration method, is provided by X9 or X12 to guarantee uniqueness of the identifier

X9 has a required minimum length of four characters for S3A05 (assurance originator). No mechanism, or registration method, is provided by X9 or X12 to guarantee uniqueness of the identifier.

Unique designation (identity) of the cryptographic process that performs validation of the stated assurance on received data. In the absence of an Assurance Recipient all potential receivers will often be able to validate the assurance because the cryptographic technique is based on a "public" (as opposed to "secret") technology Note: X9 has required minimum length of 4 characters for a security recipient; no mechanism, or registration method, is provided by X9 or X12 to guarantee uniqueness of the identifier

X9 has a required minimum length of four characters for S3A06 (assurance recipient). No mechanism, or registration method, is provided by X9 or X12 to guarantee uniqueness of the identifier.

Alphanumeric reference number issued by security assurance originator for the particular assurance in which it occurs; unique when used in combination with security originator data element

Date and time stamp in format as follows: YYYYMMDDHHNNSSTTTZZZ+XXXX, where YYYY = 4 digit year (with leading century), MM = month of year (01..12), DD = day of month (01..31), HH = hour of day in 24-hour format (00..23), NN = minutes of the hour (00-59), SS = second of hour (00..59), TTT = [optional] milli-seconds (000..999), ZZZ = [optional] three character, nominal timezone indicator (including daylight savings time indicator) and XXXXX = 3-5 digit (including leading + or - sign) offset of time to universal time, with three position format indicating hours-offset for whole hours, and five position format indicating hours and minutes offset where this is necessary. For example: 1993061522133OCDT+0930 which represents 15 June 1993, 22:13 (10:13pm), Central Daylight Time (Nominal Value "CDT"), in a timezone that is offset + 9:30 from Universal Time (Australia)

The date/time stamp may determine which of several key values apply, depending on start and expiration date of different key values that may share the same keyname.

Any text needed to convey the name of a signatory, registration number, certification number, or other assurance-originator defined or mutually-agreed business text related to the specific assurance; this text is not defined for X12 purposes and thus functions technically as "free-form text" though it may have structure that is defined by the assurance originator, an industry group, a governmental agency, or bi-laterally between assurance originator and assurance recipient

Key distribution is performed by other means and thus only onetime keys are allowed in S3A11.

The use of particular codes and corresponding values in S3A11 is dependent on the exigencies of the various cryptographic algorithms.