Format Guide
February 2011
Version 3.3
© 2002-2011 FIRST DATA CORPORATION
All Rights Reserved.
Printed in U.S.A.
Table of Contents
Part 1: STAR ISO 8583 Message Format Guide 8
Chapter 1: Introduction 9
Chapter 2: Operational Considerations 10
Overview 10
Considerations 11
Chapter 3: Message Formats 22
Message Structure 22
Message Types 22
Repeated Messages 23
Pre-authorization Messages 23
Financial Transaction Messages 25
File Maintenance Messages 26
Card Activation Messages 29
Reversal Messages 29
Administrative “Error” Messages 32
Network Management Messages 33
Bit Maps and Data Elements 34
Message Layouts 35
Bit Number and ISO Field (Data Element) Name 35
Data Type 35
Requirements – Trnsmit / Recv 37
Notes 38
Pre-authorization Messages 39
0100/0101 Pre-authorization Request 39
0110 Pre-authorization Response 46
0120/0121 Pre-authorization Advice 53
0130 Pre-authorization Advice Response 60
Financial Transaction Messages 62
0200/0201 Financial Transaction Request 62
0210 Financial Transaction Response 70
0220/0221 Financial Transaction Advice 77
0230 Financial Transaction Advice Response 85
File Maintenance Messages 87
0300 Acquirer File Update Request (Negative File) SE/W
Platforms 87
0302 Card Issuer File Update Request (Negative File) 89
0310 Acquirer File Update Response (Negative File) SE/W
Platforms 90
Introduction
This guide is intended for decision makers evaluating the STAR Network
transaction processing and the programmers and analysts who design,
implement, and support the system.
The STAR ISO 8583 Message Format Guide provides information for
processing online transactions using a standard ISO interface message
structure on all STAR processing platforms: Northeast (NE), Southeast (SE)
and West (W). It is the first book in the STAR ISO 8583 series, which consists
of the following manuals:
STAR ISO 8583 Message The STAR ISO 8583 Message Format Guide provides
Format Guide information for processing online transactions using a
standard ISO interface message structure on all STAR
processing platforms.
STAR ISO 8583 Gateway/ The STAR ISO 8583 Gateway/Product Interface Guide
Product Interface Guide provides additional processing information for
Gateway, Electronic Benefits Transfer, and STAR
Product processing.
STAR Platform Interface The STAR Platform Interface Guide is the technical
Guide interface to the STAR processing interface. Information
includes protocols, encryption standards and
telecommunications procedures. The information
presented is delineated by each STAR platform.
File Layouts Separate file layouts are variable by Platform and are
available on the STAR STATION® portal or upon
request.
Operational Considerations
Overview
The STAR ISO 8583 message format presents many opportunities for
processing and reporting. Listed below are specific considerations for clients
who are unfamiliar with ISO message formats to review to determine how
STAR ISO 8583 use will impact their business process:
■ Repeat Transactions
Considerations
Transaction Amount
■ See also Chapter 16 in this manual and the STAR ISO 8583 Gateway/
Product Interface Guide for additional information.
Currency Information
Considerations ■ All STAR terminal owners are within the US and settle in dollars;
therefore, the STAR Switch does not support currency conversion
between STAR Members.
Considerations STAR ISO 8583 processing provides a field in the request message
which identifies the type of merchant. This field is particularly important
in Point of Service (POS) transactions when determining where
cardholders are purchasing goods and services. Armed with this
information, Card Issuers can determine appropriate authorization edits
by industry and assess where cards are being used.
Considerations ■ DE 022 must be present for all POS transactions, and is optional (but
recommended) for ATM transactions.
Response Codes
Location Information
Considerations STAR ISO 8583 processing provides significantly more space for
location information than many other networks. STAR Acquirer
processors must populate both DE 043 and DE 048 in request
messages. STAR Issuer processors will be passed DE 043 and DE 048 in
all messages, thus enabling cardholder statements to list meaningful
location information. See Chapter 4 of this guide for additional
information.
Network Identifiers
■ DE 063 is also used to carry pseudo terminal IDs, processor IDs, and
processing flags that are needed to support partial amount approvals.
■ Please see Chapter 4 of this guide and the STAR ISO Gateway /
Product Interface Guide for additional information.
■ STAR ISO 8583 Acquirer Processors are required to transmit the PIN,
Track 2 Data and the Capture Date on the first submission of a
Merchant Authorized Transaction.
a. “Life of the Transaction” is defined as the initial request and response, as well as any
corrective processing associated with it such as a reversal.
Corrections/Cancellations
Routebacks
Considerations A STAR processor will find multiple records for the same transaction
when the issuing and acquiring interfaces both belong to the same
processor and all transaction activity is reported in one User File. An
Acquirer Processor may choose to route their on-us activity to the STAR
Switch, which will route it back to the processor. Note: these
transactions will be fee billed twice: once for the acquirer transaction
and once for the issuer transaction.
■ Please see Chapter 4 of this guide and the STAR ISO Gateway /
Product Interface Guide for additional information.
Considerations ■ For signature debit POS transactions, the following matching criteria
are recommended:
Platform The following criteria are recommended for matching PIN-based POS
Distinction pre-authorizations to completions on different STAR platforms.
Considerations ■ Processors must be capable of handling any and all STAR ISO data
elements in a message.
Currently, a STAR ISO message can consist of any combination of
data elements 001 through 128. If, for some reason, you receive a
message that contains a data element that is not specified in the
STAR ISO 8583 technical specifications, the processor should be
able to accept the field. In addition, processors should edit to
ensure mandatory fields are present in all message types where
indicated and include privately required fields.
■ Issuers may not send fields in the response unless they are present in
the request message or defined in the 0110 or 0210 message
layouts.
Repeat Transactions
Message Formats
Online communication of financial activity using the STAR ISO 8583 message
format takes place via highly structured messages that flow to and from the
STAR Switch. Processors, Issuers, and Acquirers must be prepared to send
and receive correctly-formatted STAR ISO 8583 messages to ensure smooth
online operations.
Message Structure
All messages in the STAR ISO 8583 processor interface consist of three
general components:
■ Message Type Identifier – a four-position numeric code beginning with
0, identifying the basic purpose of the message.
■ Bit Maps – a series of bits that indicate the presence or absence of
possible data elements in the individual message.
■ Data Elements – the bulk of the message, a collection of data items in
the order of the bit map representation.
The length of individual messages can vary depending on the number and
length of the data elements that they include.
Message Types
In the four-position Message Type ID code, the first two positions identify the
Message Class:
■ 01xx = Pre-authorization Messages
■ 02xx = Financial Transaction Messages
■ 03xx = File Maintenance Messages
■ 03xx = Card Activation Messages
■ 04xx = Reversal Messages
■ 06xx = Administrative “Error” Messages
■ 08xx = Network Management Messages
Repeated Messages
The STAR NE Platform does not support the indication of repeats in the
Message Type identifier. If the STAR NE Switch receives a repeat transaction
from an Acquirer, the transaction will be presented as the original Message
Type. For example, a 0201 received by the STAR NE Switch will be formatted
as a 0200.
Pre-authorization Messages
Disposition: Non-Financial
0130 Advice
Acknowledgement
0230 Financial
Acknowledgement
Disposition: Administrative
Note
The STAR Network’s use of the 0302 message that notifies
Issuers of updates to their card data on the STAR Negative
File is being replaced with the 0322/0332 advice messages.
Please notify your Relationship Manager if you are still
receiving the 0302 messages for the STAR Negative File
Updates and would prefer to receive the 0322 message.
STAR SE/W Platforms can optionally generate an 0300 file update request.
This message is intended to inform the Card Issuer that a cardholder PAN with
a negative status has been added to the institution’s processor’s switch
negative file that is used in stand-in and added to the debit services
(MasterCard Visa Check) Hot Card Status file.
0310 Acquirer File Update ■ Normally, a STAR processor response to the Issuer.
Response
■ STAR SE/W provides a negative file notification
service out to Issuers for any card statused by an
internal staff member. In this case, a 0310 would be
sent to STAR from the Issuer.
0312 Negative File Update ■ Normally, a STAR processor response to the Issuer.
Reply
■ STAR NE platform provides a negative file
notification service out to Issuers for any card
statused by an internal staff member. In this case, a
0312 would be sent to STAR from the Issuer.
0332 Negative File Update ■ Normally, a STAR processor response to the Issuer.
Advice
Acknowledgement ■ STAR NE provides an optional negative file
notification service out to Issuers for any card
statused by any user or application other than the
client’s or client’s initiated maintenance. Examples
would include an internal STAR staff member or CV
Denial functions. In this case, a 0332 would be sent
to STAR from the Issuer.
0392 PIN Change Reply An Issuer response to a STAR initiated PIN change
request.
0384 PIN Change Advice STAR NE: An advice notifying a cooperative processing
Issuer that a PIN change transaction was performed
and authorized on the STAR Switch. The message
contains the Cardholder’s new PIN offset.
0392 PIN Offset File Update A STAR processing response to the Issuer.
Reply
Because these message types are exclusively for Card Activation purposes,
their layouts and further information are detailed in Chapter 4 of the STAR
ISO 8583 Gateway/Product Interface Guide.
Reversal Messages
0421 Repeat Reversal Advice STAR NE does not send 0421 messages.
Disposition: Administrative
Disposition: Administrative
OR
■ 8 binary bytes (if packing of bit maps is being used)
At the bit level of the bit maps, ‘1’ bits indicate that the corresponding data
elements are “on” and should be present; ‘0’ bits indicate that the
corresponding data elements are “off” and should not be present.
All messages contain a Primary bit map. Depending on which data elements
are included, a message may also have a Secondary bit map appearing
immediately after the Primary.
Certain data elements for any Message Type are always required. However,
not all the data elements listed for a Message Type layout given in this
chapter will be found in a given instance of that message. Unnecessary data
items are omitted. Thus the bit maps are necessary to identify to the
processor interface which of all the possible data elements are present in each
particular Message Type instance.
Message Layouts
In the message layout tables that follow, each row represents a STAR data
element that may be a part of a message of that Message Type.
The message layout tables in this section have the following headings:
■ Bit
■ ISO Field Name
■ Data Type
■ Requirements – Trnsmit / Recv
■ Notes
The names shown in the ISO Field Name column are the data element
names. These names correspond to and in most cases match the ISO
8583-defined field names. There are a few instances, however—DE is an
example—in which the name shown has been modified from the ISO name to
better convey how the field is being used by STAR software.
The first two data elements, Message Type Identifier and Primary Bit Map, are
always present in any message and therefore are not numbered.
Data Type
The Data Type column of the message layout tables uses the following
indicators to describe data element attributes:
ANS Alphabetic, numeric and special characters. Left-justified with trailing spaces.
NP Numeric data element that is capable of When the numeric packing option
being packed, based on the database is set, all lengths are 1-byte
setting. The data element contains numeric binary. Odd-length packed
digits in unsigned packed format (4-bit numerics have a leading zero to
BCD) when the numeric packing option is ensure that data elements begin
set. The associated number indicates the and end on byte boundaries.
number of digits the data element contains.
LLV ■ Variable data field that can have a length ■ The maximum data element
range of 1-99. length that can be represented
by the packed 1-byte binary is
■ When the packing option is not set, the 255.
variable-length subfield is 2 numeric
characters long. Otherwise, the ■ The length of a variable-length
variable-length subfield is one byte long. field may exceed the maximum
message size defined by STAR‘s
LLLV ■ Variable data field that can have a length software. If this occurs, only the
range of 1-255. message size defined by STAR
will pass through the Switch.
■ When the packing option is not set, the
variable-length subfield is 3 numeric
characters long. Otherwise, the
variable-length subfield is one byte long.
Throughout the message layout tables that follow, the length of the
variable-length sub-element (Byte Map) is shown as if the numeric packing
option is not set. If the numeric packing option is set, all length sub-elements
are one byte long.
The 1-byte binary allows a maximum data field length of 255. With the
numeric packing database option turned on, no data field may be longer than
255.
C Conditional – The data element must be present when specific conditions are
satisfied. The applicable conditions are generally identified in the Notes
column.
O Optional – The data element is optional and may be provided at the option of
the originator of the message. If the data element is present in the message,
it may or may not be forwarded. Some elements may be unsupported.
Notes
The Notes column provides additional clarifications on the use of the element
in the online message. For a full description of each data element’s usage,
refer to Chapter 4: Data Element Definitions of this document and/or the
STAR ISO 8583 Gateway/Product Interface Guide.
MM Month (01-12)
DD Day (01-31)
YY Year (00-99)
hh Hour (00-23)
mm Minute (00-59)
ss Second (00-59)
Pre-authorization Messages
■ ‘0101’ if repeated by
Acquirer.
■ If electronically
captured, DE 035 or
DE 045 must be
present.
■ MMDDhhmmss
■ YYMM
■ MMDD
■ Return if available.
■ MMDD
027 Authorization N1 O C
Identification Response
Length
■ Applicable only on
Acquirer side.
■ May optionally be
passed to signature
debit issuers. STAR
acquirers should not
send this data.
■ If electronically
captured, DE 035 or
DE 045 will be present.
■ Only present if
required by or
transmitted from
another network.
■ MMDDhhmmss
■ hhmmss
■ MMDD
■ YYMM
■ MMDD
■ Return if available.
■ MMDD
025 Point-Of-Service N2 O O
Condition Code
■ May be returned, if
received in the
request, if the
Card-Issuer Processor
desires to have this
field returned in a
reversal.
■ Only present if
required by or
transmitted from
another network.
■ ‘0121’ if repeated.
■ MMDDhhmmss
■ hhmmss
■ MMDD
■ YYMM
■ MMDD
■ MMDD
■ MMDD
■ May be present if
transmitted in the
01xx.
■ May optionally be
passed to signature
debit issuers. STAR
acquirers should not
send this data.
■ MMDDhhmmss
■ hhmmss
■ MMDD
■ MMDD
■ ‘0201’ if repeated by
Acquirer Processor.
■ If electronically
captured, DE 035 (or
DE 045 from non-STAR
Acquirers) must be
present.
■ MMDDhhmmss
■ YYMM
■ MMDD
■ MMDD
■ MMDD
027 Authorization N1 O C
Identification Response
Length
■ Applicable only on
Acquirer side.
■ May optionally be
passed to signature
debit issuers. STAR
acquirers should not
send this data.
■ If electronically
captured, DE 035 or
DE 045 will be present.
■ Only present if
required by or
transmitted from
another network.
■ MMDDhhmmss
■ hhmmss
■ MMDD
■ MMDD
■ Returned if available.
■ MMDD
■ MMDD
025 Point-Of-Service N2 O O
Condition Code
■ Provides enhanced
balance amounts, text,
and other information.
■ For Receiver/Send
Data, also see Chapter
13 in this manual and
Chapter 12 in the STAR
ISO 8583 Gateway/
Product Interface
Guide.
■ May be returned, if
received in the
request, if the
Card-Issuer Processor
desires to have this
field returned in a
reversal.
■ Only present if
required by or
transmitted from
another network.
■ MMDDhhmmss
■ hhmmss
■ MMDD
■ MMDD
■ MMDD
■ Applicable only on
Acquirer side.
■ Sent to Card-Issuer
Processors if available
(as non-STAR
networks may not
send).
■ MMDDhhmmss
■ hhmmss
■ MMDD
■ MMDD
■ MMDDhhmmss
Table 3.19: 0300 Acquirer File Update Request (Negative File) SE/W
Platforms (cont.)
Requirements
Bit ISO Field Name Data Type Trnsmit Recv Notes
■ '2' = Update
■ '3' = Delete
■ MMDDhhmmss
■ MMDDhhmmss
■ MMDDhhmmss
‘2’ = Update
‘3’ = Delete
■ ‘2’ = Change
■ ‘3’ = Delete
■ Values:
◆ ‘CH01’ - Cardholder
information
◆ ‘CH02’ - Track II
information
■ Cardholder file
maintenance data.
◆ Blank spaces =
Existing data does
not change
◆ Asterisks = Existing
data is blanked out
(for alpha and
alpha-numeric fields
only).
◆ Other characters or
text = Existing data
is replaced with the
new data.
Reversal Messages
■ MMDDhhmmss
■ hhmmss
■ MMDD
■ YYMM
■ MMDD
■ MMDD
■ Applicable only on
Acquirer side.
■ MMDDhhmmss
■ hhmmss
■ MMDD
Administrative Messages
■ MMDDhhmmss
■ MMDDhhmmss
■ MMDDhhmmss
Options available to Processors using the STAR ISO 8583 message format:
Data Elements
– Message Type
STAR Element Format NP-4
Processing Rules ■ This data element is conditional on the presence of one or more
data elements in the range 065-128.
Acquirer
■ 03xx Required
Issuer
Processing Rules Required if Point of Service Entry Mode (DE 022) indicates that
the PAN was manually entered.
Acquirer/Issuer
‘40’ Transfer
Acquirer/Issuer
■ For the 0420 “1F” Reversal Advices that an issuer will receive
for transactions involving a MasterCard CCA fee, DE 004 will
reflect the adjusted local transaction amount. The DE 004
amount is for informational use only.
Acquirer/Issuer
■ For the 0420 “1F” Reversal Advices that an issuer will receive
for transactions involving MasterCard CCA fees, DE 005 will
reflect the same value the issuer returned in the response
message. DE 005 is for informational use only. Issuer Note:
The posting of this transaction should be done from the
replacement amount in DE 095.
Issuer
Acquirer
■ 0110, 0210, 0130, Conditional May be received for transactions for non-US
0230, 0430 cardholders.
◆ For the 0420 “1F” Reversal Advice that an issuer will receive
for transactions involving MasterCard CCA fees, DE 006 will
reflect the same value the issuer returned in the response
message. Issuer Note: The posting of this transaction should
be done from either the replacement settlement amount in
DE 095 or the equivalent amount obtained by summing DE
006 and the replacement CCA fee in DE 056.
Platform Distinction This data element is not available on the STAR NE platform.
Definition Date and time the message entered into the data interchange
system. To be expressed in Greenwich Mean Time (GMT).
Updated by each processor end point.
Definition The factor used by the network that performs the currency
conversion in the conversion from the transaction amount to
settlement amount. The Amount, Transaction (DE 004) is
multiplied by DE 009 to determine Amount, Settlement (DE 005).
Acquirer
Issuer
■ 010x, 012x, 020x, Conditional Will be sent to U.S. Issuers when value is
022x, 042x other than '840'.
Definition The factor used by the network that performs the currency
conversion in the conversion from the Amount, Transaction
(DE 004) to Amount, Cardholder Billing (DE 006). DE 004 is
multiplied by DE 010 to determine Amount, Cardholder Billing
(DE 006).
Issuer
Acquirer
■ 0110, 0210, 0130, Conditional May be received for transactions for non-US
0230, 0430 cardholders.
Platform Distinction On the STAR NE Platform, this field is not provided in the online
message.
Acquirer
■ 0100, 0200, 0220, All must have the Must remain unchanged throughout the Life
0420 same trace of the Transaction.
number.
Processing Rules The System Trace Audit Number is assigned by the STAR
processor and must be unique for every request, original
submission and resubmission sent to the STAR Switch.
Definition The local time at which the transaction takes place at the point of
card/check acceptor location.
Message Type Format Disposition Condition
Acquirer
Processing Rules ■ Must remain unchanged throughout the Life of the Transaction.
Platform Distinction On the STAR NE Platform, 022x may have zeros for time.
Definition The local month and day on which the transaction takes place at
the card/check acceptor location.
Message Type Format Disposition Condition
Acquirer
Definition The year and month after which the card expires.
Message Type Disposition Condition
Acquirer/Issuer
■ 010x, 012x, 020x, Optional May be sent if PAN is manually entered and
022x, 042x the data is readily available (embossed on
card face).
Definition The month and day funds will be transferred between Acquirer
Processor and Card-Issuer Processor/Card-Issuer or any
intermediate network facility.
Acquirer/Issuer
Definition The month and day the conversion rate is effective to convert the
Amount, Transaction (DE 004) and, if present Amount,
Transaction Fee (DE 028) to settlement currencies.
Message Type Disposition Condition
Issuer
■ 0110, 0210, 0130, Conditional May be received for transactions for non-US
0230, 0430 cardholders.
Platform Distinction
Definition The month and day the transaction is processed by the Acquirer
Processor. This is the Acquirer Processor's calendar day.
Message Type Disposition Condition
Acquirer/Issuer
Processing Rules If the difference between the current STAR Switch date and
current local date exceeds 12 calendar days, the STAR Switch will
reject the transaction with response code ‘80’ (stale dated
transaction).
Acquirer
Issuer
Processing Rules ■ If an Acquirer Processor blank-fills this field, the STAR Switch
will fill this field with zeros.
Definition The code of the country where the acquiring institution is located
(see ISO 3166).
Message Type Disposition Condition
Acquirer
Issuer
Definition First two positions indicate the method by which the Primary
Cardholder Account Number was entered into the system. The
third position indicates PIN entry capabilities.
Message Type Disposition Condition
Acquirer
Issuer
‘01’ Manual
■ The STAR SE/W Switch will not perform Stand-in, nor can a
merchant/POS processor perform Stand-in, if:
Acquirer/Issuer
Processing Rules If the Issuer accepts Visa Card Sequence Number, then DE 023
will be populated with Visa Card Sequence Number ID.
Definition The conditions under which the transaction takes place at the
point of sale (POS).
Acquirer/Issuer
■ 042x Optional
Acquirer/Issuer
Acquirer/Issuer
Acquirer/Issuer
Acquirer/Issuer
■ 010x, 0110, 012x, Required All STAR ATM and POS Acquirer Processors
020x, 0210, 022x, must format the FRDABA as 1NNNNNNNNC,
042x where NNNNNNNN is the FRDABA and C is a
check digit.
Processing Rules ■ If the element begins with a ‘1’, must be an FRDABA with a
valid check digit. The check digit will be calculated using a
weighting factor of 37137137.
Platform Distinction ■ For STARsf acquired transactions on the SE-W platform, this will
be a pseudo ABA assigned by the network. As a result,
acquirers will be returned an acquirer network ID of ‘SSF’ in
DE063 of the 0210 response to STARsf ATM withdrawal
transactions. Issuers will be sent an acquirer network ID of
‘SSF’ in DE063 of the 0200 withdrawal message.
033 Sponsor ID
STAR Element Format LLV N-11
ATM Acquirer
POS Acquirer
Processing Rules ■ Must be a numeric value. All zeros is an acceptable value for
transactions that are not sponsored.
Acquirer
Issuer
Acquirer/Issuer
Processing Rules ■ STAR Acquirers are required to send the same value in DE 037
in both filled purchase pre-authorization requests and the
associated pre-authorized completions.
Acquirer
Issuer
■ Issuers should not use an 'N' or an 'S' in the first position of this
field as these designations are used when STAR processing (vs.
the Card-Issuer processor) populates DE 038. Doing so could
cause confusion to the Acquirer Processor as to whether the
Switch or the Card-Issuer Processor denied the transaction.
Acquirer/Issuer
Processing Rules ■ When Response Code is 30, Additional Response Data (DE 044)
will/must contain the data element number that is in error.
Acquirer
Acquirer
■ 010x, 012x, 020x, Conditional STAR point of sale and bill payment Acquirer
022x, 042x Processors must supply a unique value for
each merchant or merchant location.
Issuer
■ 1-23 Address
■ 24-36 City
Acquirer
Issuer
Acquirer
Issuer
Acquirer/Issuer
■ 1-10 phone
Issuer
Processing Rules See the STAR ISO 8583 Gateway/Product Interface Guide for
information on how DE 044 is used in response messages for the
STAR CHEK® Direct.
Platform Distinction DE 044 is not used with negative file status inquiries on the STAR
NE platform.
Issuer
Acquirer/Issuer
Processing Rules ■ See the STAR ISO 8583 Gateway/Product Interface Guide for
additional information.
Definition Name of the Member financial institution that owns the ATM, or
name of the Merchant where the POS terminal is located or the
ATM sponsoring institution.
Message Type Disposition Condition
Acquirer
Issuer
Processing Rules ISO Acquirer Processors should limit the use of special characters.
Definition Code defining the local currency of the acquirer. The currency
used in Amount, Transaction (DE 004) and Amount, Transaction
Fee (DE 028).
Message Type Disposition Condition
Acquirer/Issuer
Definition Code defining the currency of Amount, Settlement (DE 005) and
Amount, Settlement Fee (DE 029).
Message Type Disposition Condition
Acquirer/Issuer
Issuer
Acquirer
■ 0110, 0210, 0130, Conditional May be received for transactions for non-US
0230, 0430 cardholders.
Acquirer/Issuer
Acquirer
◆ STAR NE Platform:
■ STAR NE Platform:
◆ STAR NE Platform:
◆ STAR NE Platform:
Issuer
◆ STAR NE Platform
◆ STAR NE Platform:
■ Right-justified, zero-filled
Processing Rules ■ Issuer Members shall not transmit through the STAR Network
any positive Available Balance or POS Balance that includes
amounts available through an overdraft protection program,
other than a line of credit that is subject to Regulation Z, in
response to an Authorization request for a Balance Inquiry or
for any other purpose.
■ The sign indicator for STAR cash back amounts should be set to
‘C’ (positive amount).
◆ Balance Amount
Issuer
■ 010x, 012x, 020x, Optional / For Issuers who have opted to receive this
022x, 042x Conditional field, it will be present when any additional
fee amounts are available in the message.
■ 0110, 0130, 0210, Conditional Required if the Additional Fees data element
0230, 0430 is received in the request. The response
value must be the same as the value in the
request.
■ ‘15’ = Currency
Conversion
Assessment (CCA
fee). First amount
is in cardholder bill
currency and
second amount is
in settlement
currency.
■ It is also
appropriate to not
charge the
cardholder
separately for fee
type ‘15’ (CCA) as
this fee is already
contained in the
transaction
amount.
■ '1' = Card-Issuer
processor should
apply this fee (in
addition to the
transaction
amount) to the
cardholder
account. Such
handling is
appropriate for
surcharge fees. (At
this time, STAR
uses only DE 028
and DE 029 for
surcharge fees.)
■ X (sign indicator):
Issuer
■ ‘15’ = Currency
Conversion
Assessment
(MasterCard CCA
fee). The first
amount is in the
cardholder bill
currency and the
second amount is
in the settlement
currency.
It is also appropriate
to not charge the
cardholder
separately for fee
type ‘15’ (CCA) as
this fee is already
contained in the
transaction amount.
‘1’ = Card-Issuer
processor should
apply this fee (in
addition to the
transaction amount)
to the cardholder
account. Such
handling is
appropriate for
surcharge fees. (At
this time, STAR uses
only DE 028 and DE
029 for surcharge
fees.)
■ X (sign indicator):
Acquirer/Issuer
‘2’ = Hours
‘3’ = Minutes
Acquirer/Issuer
Processing Rules ■ See Chapter 11: Data Element 058: National Point of Service A
for additional information.
Acquirer
■ 010x, 012x, 020x, Conditional This is a mandatory data element for some
022x, 042x networks (access to which may be provided
by STAR).
Issuer
Acquirer/Issuer
■ Formats:
Processing Rules ■ For a reversal, STAR Acquirer Processors should send only a
reversal reason
Definition Free format data of up to 100 bytes that will be echoed to the
Acquirer Processor in the response to their request.
Message Type Disposition Condition
Acquirer/Issuer
Processing Rules This field will not be passed on to the Card-Issuer Processor.
Definition Free format data of up to 100 bytes that will be echoed to the
Card-Issuer Processor in response to their request.
Message Type Disposition Condition
Acquirer/Issuer
Processing Rules ■ This field will not be passed on to the Acquirer Processor.
Length Description
6 1/1 Processor ID 4
■ Position 1:
Externally settled
transaction
indicator (not used
for STAR
transactions).
◆ Values = Space
or ‘0’
◆ Position 2:
Reserved for
Future Use
■ Value = Space
■ Position 3:
Merchant partial
amount approval
capability.
Values:
◆ Space or ‘0’:
Merchant
terminal does
not support
receipt of partial
approvals.
◆ 1: Merchant
terminal
supports receipt
of partial
approvals.
■ Positions 4-5:
Reserved for future
use.
Pseudo Terminal ID
Acquirer/Issuer
Issuer Network ID
Issuer
Acquirer
Acquirer Network ID
Issuer
■ STAR NE:
Mandatory for
Issuers to receive.
◆ When acquirer
processor
represents a link
to another
non-STAR
network.
■ STAR NE platform:
Not used.
◆ With STAR
CHEK® Direct
product.
◆ When acquirer
processor
represents a link
to another
non-STAR
network.
◆ When received in
response.
■ STAR NE platform:
Not used.
Processor ID
Acquirer/Issuer
Acquirer
Issuer
■ On the STAR SE-W Platforms, the value is not edited and will be
changed at STAR to a STAR-assigned value (which is associated
with data provided by the Acquirer in De 032 and DE 058). For
this reason, the pseudo terminal value contained in STAR SE-W
settlement user files may not match the value supplied in the
request.
Processor ID:
Processing Flags:
Acquirer/Issuer
Acquirer/Issuer
Processing Rules ■ The first three sub-elements are supported by STAR. The
remaining two sub-elements must be zero-filled. If an Acquirer
Processor zero-fills either the Original system trace audit
number or the Original transmission date and time, the Switch
will replace the zeros with data contained from DE 011 and
DE 007.
Acquirer/Issuer
‘5’ Inquiry
Acquirer/Issuer
Acquirer/Issuer
Definition Unique to STAR CHEK® Direct. This field is used to determine the
authorization entity for routing.
Message Type Disposition Condition
Acquirer/Issuer
■ 0100, 0120, 0200, Required All STAR CHEK® Direct check transactions.
0220, 0420
Processing Rules Should contain the check’s 9-digit Routing and Transit number.
Acquirer/Issuer
■ 0302 Required
STAR NE Acquirer:
■ 0302:
■ 0312:
■ 0382:
■ 0392:
STAR NE Issuer:
■ 0302:
■ 0322:
■ 0382:
■ 0384:
Acquirer/Issuer
Acquirer/Issuer
Acquirer
Issuer
■ 010x, 012x, 020x, Conditional ■ Will be sent to issuer for POS transactions.
022x, 042x
Acquirer/Issuer
Processing Rules ■ See Chapter 12: Data Element 105: Large Private Data in this
manual for information on current usages of DE 105.
Definition This tagged data field is used to carry information from and about
the sender of the transaction.
Message Type Disposition Condition
Issuer
Processing Rules ■ See the STAR ISO 8583 Gateway/Product Interface Guide,
Chapter 12 for details on how this element is used in
transactions.
Acquirer
Issuer
■ 010x, 012x, 020x, Optional For STAR Issuers, in certain instances and
022x, 042x upon request, STAR can pass DE 111 to
convey information received from other
networks
Processing Rules See the STAR ISO 8583 Gateway/Product Interface Guide,
Chapter 8, DE111: Additional Data, Private Acquirer for detailed
information on uses, formats, and platform distinctions for this
data element.
Issuer
■ 0110, 0210 Required ■ All STAR ATM & POS issuing processors
must format the FRD-ABA as
1NNNNNNNNC where NNNNNNNN is the
FRD-ABA and C is a check digit.
Acquirer
■ STAR SE = 1111111111
■ STAR W = 1605460540
■ STAR NE = 1031000011
Issuer
Acquirer
■ 0110, 0130, 0210, Conditional May be received for transactions for non-US
0230, 0430 cardholders.
Acquirer/Issuer
◆ 1nn = Checking
◆ 2nn = Savings
◆ 3nn = Credit
◆ 4nn = Other
Acquirer/Issuer
Acquirer
Issuer
Issuer
■ 010x, 012x, 020x, Optional For the Issuers electing to receive it, DE 122
022x, 042x can carry MasterCard acquirer Customer ID
or VISA Sponsor Bank ID values.
Platform Distinction This field is for STAR SE/W Issuers only; it is not applicable for
the STAR NE Platform.
Definition This data element can carry data for several purposes:
◆ MICR data
Acquirer/Issuer
Cash/Check Deposit
■ 0200, 0220, 0420 Conditional Issuers must be able to receive and send for
cash/check deposit authorizations.
Processing Rules When using the Tagged Data format, multiple components, such
as AVS and CVV2 data, may appear in a single message and vary
in their order. The Format Type identifier ‘TD’ must occupy
positions 1-2 of the element for all tagged formats.
Platform Distinction STAR NE Platform supports AVS through this data element only in
the Tagged Data format.
Acquirer/Issuer
AN 41 Filler (spaces)
Platform Distinction ■ Card Activation and PIN Change/Offset usage is available on the
STAR NE platform only.
Acquirer/Issuer
Acquirer
Issuer
0110, 0210 Conditional May be returned, if received in the request (if the
Card-Issuer Processor wants to receive this field in
a reversal for a late response).
Acquirer
Issuer
Acquirer
Issuer
■ 010x, 012x, 020x, Optional For STAR Issuers, in certain cases and upon
022x, 042x request, STAR can pass DE 127 in request
messages.
Processing Rules See the STAR ISO 8583 Gateway/Product Interface Guide,
Chapter 7, Data Element 127: Acquirer Trace Data for additional
information.
Message Type –
Format Options
ASCII/EBCDIC Table
Table 6.2: ASCII/EBCDIC Characters/Codes
dec hex binary ASCII EBCDIC
2 0x02 0000 0010 STX Start of Text (CC) STX Start of Text
3 0x03 0000 0011 ETX End of Text (CC) ETX End of Text
16 0x10 0001 0000 DLE Data Link Escape DLE Data Link
(CC) Escape
Step 5: Subtract the sum of the products from the next highest or equal multiple of 10. The
remainder is the check digit. Zero is a valid check digit.
Example
To find the value of the check digit (X) using the example ABA 12210001X:
30 - 29 = 1
Luhn Formula
Used for computing a modulus 10 “double-add-double” check digit.
Step 1: Double the value of alternate digits beginning with the first right-hand digit (low
order).
Step 2: Add the individual digits that make up the products obtained in Step 1 to the
unaffected digits in the original number.
Step 3: Subtract the total obtained in Step 2 from the next higher number ending in 0. This
is the equivalent of calculating the “tens complement” of the low order digit (unit
digit) of the total.
If the total obtained in Step 2 is a number ending in zero (30, 40, etc.), the check
digit is 0.
Example
To find the value of the check digit (X) using the example account number
4992 73 9871 X:
Step 1: 4 9 9 2 7 3 9 8 7 1
×2 ×2 ×2 ×2 ×2
18 4 6 16 2
70 - 64 = 6
Note
See the STAR ISO 8583 Gateway/Product Interface Guide for
additional processing codes that are supported due to participation in
other networks.
ATM
Mandatory (Issuer/Acquirer)
Table 7.1: ATM Mandatory Proc Codes
Description ISO Proc Code Message Notes
Optional (Issuer/Acquirer)
Table 7.2: ATM Optional Proc Codes
Description ISO Proc Code Message Notes
Account List Inquiry from SAV 35 10 00 0100, 0110 STAR NE Platform only.
Account List Inquiry from DDA 35 20 00 0100, 0110 STAR NE Platform only.
Account List Inquiry from CRD 35 30 00 0100, 0110 STAR NE Platform only.
Account List Inquiry from OTH 35 09 00 0100, 0110 STAR NE Platform only.
Point of Sale
Optional
Table 7.5: POS Optional Proc Codes
Description ISO Proc Code Message Notes
This Chapter lists Merchant Type codes (also known as Merchant Category
codes or SIC codes). The first table is in numerical order; the table beginning
on page 276 gives an alphabetical listing.
3008 Lufthansa—LUFTHAN
3011 Aeroflot—AEROFLOT
3012 Qantas—QANTAS
3013 Alitalia—ALITALIA
3019 Germanwings—GRMNWNGSAIR
3023 Mexicana—MEXICANA
3032 El Al—EL AL
3037 EgyptAir—EGYPTAIR
3039 Avianca—AVIANCA
3042 Finnair—FINNAIR
3050 Icelandair—ICELANDA
3058 Delta—DELTA
3061 Continental—CONTINEN
3076 Aeromexico—AEROMEXI
3089 Transaero—TRANSAERO
3097 Spanair—SPANAIR
3102 Iberia—IBERIA
3146 Luxair—LUXAIR
3164 Norontair—NORONTAI
3184 LIAT—LIAT
3223 Comair—COMAIR
3240 Bahamasair—BAHAMASA
3242 Avensa—AVENSA
3246 Ryanair
3293 Ecuatoriana—ECUATORI
3357 Hertz
3412 A1 Rent-A-Car
3509 Marriott
3514 Amerisuites
3615 Travelodge
3634 Swissotel
3644 EconoLodges
3700 Motel 6
3722 Wyndham—WYNDHAM
3779 W Hotels
3808 LXR
3822 Crossland
4011 Railroads—Freight
5462 Bakeries
5811 Caterers
5992 Florists
6211 Securities—Brokers/Dealers
7012 Timeshares
7251 Hat Cleaning Shops, Shoe Repair Shops, Shoe Shine Parlors
7394 Equipment Rental and Leasing Services, Furniture Rental, Tool Rental
8041 Chiropractors
9222 Fines
3412 A1 Rent-A-Car
3011 Aeroflot—AEROFLOT
3076 Aeromexico—AEROMEXI
3013 Alitalia—ALITALIA
3514 Amerisuites
3242 Avensa—AVENSA
3039 Avianca—AVIANCA
3240 Bahamasair—BAHAMASA
5462 Bakeries
5811 Caterers
8041 Chiropractors
3223 Comair—COMAIR
3061 Continental—CONTINEN
3822 Crossland
3058 Delta—DELTA
3644 EconoLodges
3293 Ecuatoriana—ECUATORI
3037 EgyptAir—EGYPTAIR
3032 El Al—EL AL
7394 Equipment Rental and Leasing Services, Furniture Rental, Tool Rental
9222 Fines
3042 Finnair—FINNAIR
5992 Florists
3019 Germanwings—GRMNWNGSAIR
7251 Hat Cleaning Shops, Shoe Repair Shops, Shoe Shine Parlors
3357 Hertz
3102 Iberia—IBERIA
3050 Icelandair—ICELANDA
3184 LIAT—LIAT
3808 LXR
3008 Lufthansa—LUFTHAN
3146 Luxair—LUXAIR
3509 Marriott
3023 Mexicana—MEXICANA
3700 Motel 6
3164 Norontair—NORONTAI
3012 Qantas—QANTAS
4011 Railroads—Freight
3246 Ryanair
6211 Securities—Brokers/Dealers
3097 Spanair—SPANAIR
3634 Swissotel
7012 Timeshares
3089 Transaero—TRANSAERO
3615 Travelodge
3779 W Hotels
3722 Wyndham—WYNDHAM
‘04’ Pick-up
‘10’ Approved for Partial Amount Valid for POS transaction repsonses
(provided the aquiring network supports
partial amount approvals).
■ Processed as an approval.
‘24’ File update not supported by Used only for Negative File Updates
receiver (0312).
‘27’ File update edit error Used only for Negative File Updates
(0312).
‘28’ File update file locked out Used only for Negative File Updates
(0312).
‘29’ File update not successful, contact ■ Negative File Updates (0312).
Acquirer
■ Card Activation (0382).
‘35’ Card acceptor contact Acquirer Unsupported for STAR network, may be
(Capture) used by other networks. Processing will
be governed by other network’s rules.
‘37’ Card acceptor, call Acquirer security Unsupported for STAR network, may be
(Capture) used by other networks. Processing will
be governed by other network’s rules.
‘60’ Card acceptor contact Acquirer Unsupported for STAR network, may be
used by other networks. Processing will
be governed by other network’s rules.
‘66’ Card acceptor call Acquirer's security Unsupported for STARnetwork, may be
department used by other networks. Processing will
be governed by other network’s rules.
‘81’ Issuer not available to authorize ■ STAR NE Platform: STAR will stand-in
for Issuer if option is set at STAR
Network to do so.
‘82’ Count exceeds limit (valid only for Unsupported for STAR network, may be
VisaNet Issuers) used by other networks. Processing will
be governed by other network’s rules.
‘84’ Time for pre-authorization reached Unsupported for STAR network, may be
(Only valid for Interlink Issuers) used by other networks. Processing will
be governed by other network’s rules.
‘86’ Cannot verify PIN (valid only for Unsupported for STAR network, may be
VisaNet Issuers) used by other networks. Processing will
be governed by other network’s rules.
‘87’ Duplicate
■ Cutoff in progress
STAR NE Platform:
◆ Track 2
* These codes are those for which the Acquirer Processor will receive no
interchange fee and the Card-Issuer Processor will not be charged an
interchange fee or a Switch fee. The no-fee designation applies only to STAR
SE/W transactions when the transaction is denied by the STAR Switch.
Transactions rejected by the STAR Switch can be identified by the acquirer
based upon there being a value of ‘N’ or 'S' in Authorization Response Code
(DE 038) of the 0110/0210 response message.
Overview
Data Element 054, Additional Amounts, is used to clarify the following:
■ Balances: Used to provide varying balance and credit line amounts.
Required for balance inquiry responses; optional in responses to other
transaction types.
■ Deposits: Used to support verified and unverified, cashed check and cash
deposits (Amount Types ‘92’, ‘93’, ‘94’, and ‘95’).
■ Partial Amount Authorization:
◆ For PIN-based POS pre-authorization transactions for Processors using
the original partial authorization methodology, this data element is
used in 0110 responses to convey the authorized amount (Amount
Type = ‘58’).
◆ For all stand-alone POS purchase transactions, and for POS
pre-authorization transactions for Processors using the new partial
authorization methodology, this data element is used in 0110/0210
responses to convey the amount of the original request (Amount Type
= '91').
■ Point of Banking: Used to convey the composition of a deposit for a POB
deposit (Amount Types ‘42’ and ‘43’).
■ POS Cash Back Support: Amount of cash given to customer – required if
cash back is given. If POS is only used for cash back, the entire amount of
the transaction must be represented as cash in DE 054 (Amount Type =
‘40’).
■ Pre-authorized Amount Completion: For a PIN-based POS
pre-authorized transaction completion, this data element is used in the
022x completion to convey the original authorized amount from the 0110
message (Amount Type = ‘57’).
■ Quasi-cash and Scrip: Acquirer processors who sell items that can be
negotiable for cash (money orders, postal orders, gaming chips, POS scrip,
etc.), must present the total dollar amount of the negotiable items (as
conveyed in DE 004) in DE 054. Amount Type in DE 054 must be set to
‘40’ (cash back). This must be present in all request, advice, and reversal
messages.
If the STAR SE/W card-issuer processor does not support the new partial
authorization methodology, then for a pre-authorization reply (0110) for a
transaction for which sufficient funds are not available to accommodate the
full transaction amount (DE 004) requested, the Issuer Processor should
return the available balance or available limit in DE 054 using Amount Type =
'58'.
Note that STAR SE/W does not support partial authorization of purchase
transactions using the old partial authorization methodology.
For either methodology Response Code (DE 039) must be set to '10'. A
Card-Issuer Processor must not return a partial authorization response if the
available balance or available limit is:
■ Equal to or greater than DE 004;
■ Equal to zero; OR
■ Negative.
STAR NE Platform
On a pre-authorization reply (0110) or purchase reply (0210) for a transaction
for which sufficient funds are not available to accommodate the full
transaction amount (DE 004) requested, the STAR NE POS Card-Issuer
Processor should return the available balance or available limit in DE 054
using Amount Type '58'. Response Code (DE 039) must be set to '10'. A
Card-Issuer Processor must not return Amount Type '58' in DE 054 if the
available balance or available limit is:
■ Equal to or greater than DE 004, with the following exceptions:
◆ Automated Fuel Pump (AFD) preauthorization (DE 018 = 5542) in
which the cardholder's balance is below the standard AFD floor limit.
◆ Visa Prestigious Properties preauthorization in which the cardholder's
balance is below the authorization limit indicated by the Prestigious
Properties Indicator in DE 127. For a description of this field refer to the
section entitled "Visa Check: STAR NE Platform Format" in Chapter 7 of
the STAR ISO 8583 Gateway Product Interface Guide.
◆ For either of these scenarios, the issuer may return a partial
authorization with authorized amount greater than the requested
amount and less than the indicated floor limit.
■ Equal to zero.
■ Negative.
Account Type
Positions 1 and 2 of each amount give the ISO code that defines the Account
Type:
‘00’ Default
Amount Type
Positions 3 and 4 give the ISO code that defines the Amount Type:
‘40’ Amount of Cash or 010x, 020x, ■ Required if cash is given with transaction
Negotiable Items 0210, 022x, (cash back).
Given to the 042x
Customer ■ Required if Negotiable Items (items that
can be negotiable for cash—e.g., money
(Cash Back) orders, postal orders, gaming chips and
POS scrip) are given with the
transaction.
‘58’ Authorized Amount 0110, 0210 Used for POS Used for POS
pre-authorization pre-authorization
and purchase transactions, for
transactions to Processors using the
convey the original partial
authorized amount. authorization
methodology, to
convey the
authorized amount.
‘91’ Amount of original 0110, 0210 Not available For partial amount
request authorizations for all
stand-alone POS
purchase
transactions, and
for POS
pre-authorization
transactions for
Processors using the
new partial
authorization
methodology, this
data element is to
convey the amount
of the original
request.
Cash Deposit
Amount (STAR SE/
W Platform)
Check Deposit
Amount (STAR SE/
W Platform)
Currency Code
Processors should query the currency code field in each occurrence of an
additional amount, as occurrences with non-US values may be present.
Amount
Positions 8-20 reflect the sign and the specific amount:
X + n12
■ ‘D’
0 Attended
1 Unattended
0 Customer Operated
1 Merchant Operated
2 Administrative
0 On Premise
1 Off Premise
0 Customer present
8* ■ Pre-authorized purchase
0 Card present
8* ■ Pre-authorized purchase
0 Original Presentment
7 Reapplies (STAR NE Platform only). See the CMA User Guide for additional
information.
0 No security concern
1* Suspected fraud
2* Identification verified
00 Administrative terminal
02 ATM terminal
07 Fuel Machine
09 Coupon machine STAR SE/W Acquirers may not send this value.
10 Ticket machine STAR SE/W Acquirers may not send this value.
12 Teller
13 Franchise teller STAR SE/W Acquirers may not send this value.
14 Personal banking STAR SE/W Acquirers may not send this value.
15 Public utility STAR SE/W Acquirers may not send this value.
0001104007 Merch Auth Fuel Disp 0100004008 Merch Auth Scrip Terminal
0101104007 Merch Auth Fuel Disp 0110004008 Merch Auth Scrip Terminal
0111104007 Merch Auth Fuel Disp 1000004008 Merch Auth Scrip Terminal
1101104007 Merch Auth Fuel Disp 1010004008 Merch Auth Scrip Terminal
1111104007 Merch Auth Fuel Disp 1100004008 Merch Auth Scrip Terminal
Reversal Reason
In general, Position 1 identifies who reversed the given transaction; Position 2
gives the reason for the reversal.
‘5-8’ Reserved.
STAR Card Issuer Processors transmitting 0110 or 0210 responses that fail
STAR Switch data element edits will receive a 0420 reversal message with a
reversal reason code of ‘30’
Advice Reason
In general, position 1 indicates who stood in for this transaction; Position 2
values indicate why the transaction stand-in occurred.
4-8 Reserved
‘C’ Card Validation Threshold Service denial advice (STAR NE platform only).
‘1’-’3’ ‘7’ POS switch authorized under floor limit (not applicable to
STAR transactions)
The following table lists the current values for the STAR Interchange Group.
Position Interchange
1 2 3 Description Group
B K Balance Inquiry
(PINless)
A D Bill Payment
A E Bill Payment
A F Bill Payment
Position Interchange
1 2 3 Description Group
A X Contactless Medical
Merchant <$15
Position Interchange
1 2 3 Description Group
A 8 Contactless petroleum 1
merchant <$25.
A 9 Contactless petroleum 2
merchant <$25.
A 0 Contactless petroleum 3
merchant <$25.
B A Contactless petroleum 1
merchant >$25.
B B Contactless petroleum 2
merchant >$25.
B C Contactless petroleum 3
merchant >$25.
A Z Contactless Quick
service restaurant
<$25.
A 1 Contactless Quick
service restaurant
>$25.
A M e-Commerce
A N e-Commerce
B I eCommerce Refund
Position Interchange
1 2 3 Description Group
H Grocery 1B (Target) -
Special
K Interbank/Funds
Transfer (credit side)
I Internet eSign
2 Medical
Position Interchange
1 2 3 Description Group
A J Mobile Payments
A K Mobile Payments
A O Online Refund
A G Pay at Table
O Petroleum 1
R Petroleum 2
V Petroleum 3
T Petroleum - Special 2
F Petroleum - Special
G Petroleum - Special
A B Pre-Paid Load
Transaction
E Project Coronado
A A Project Coronado - 2
B N Purchase (PINless)
Position Interchange
1 2 3 Description Group
3 Small Ticket
B L Transaction History
(PINless)
B H Transaction Refund
A L Verification Transaction
B F WEB Micropayments
Acquirer/Issuer
NSS
where N is one of
these values:
■ ‘1’ = Checking
■ ‘2’ = Savings
■ ‘3’ = Credit
■ ‘4’ = Other
SS is the sequence
number of the
account. Valid values
are ‘01’ through ‘99’.
A value of ‘01’
indicates that this is
the primary account
of the type indicated.
The Data Detail segment can occur up to 8 times, totaling 176 bytes
maximum. For all ALI transactions, at least one occurrence of the Detail
segment must follow the Fixed segment, beginning in position 10 of DE 105.
Because there may be several occurrences, the position numbers given above
are relative to the segment.
Acquirer/ Issuer
■ ‘Y’ = Balance
Amount is to be
used
■ ‘N’ = Balance
Amount is not
applicable
-NNNNNNNN –
where “-” is a
high-order negative
sign, followed by an
8-digit ($$$$$$DD)
negative amount
OR
NNNNNNNNN – a
9-digit ($$$$$$$DD)
positive amount.
NSS
■ ‘1’ = Checking
■ ‘2’ = Savings
■ ‘3’ = Credit
■ ‘4’ = Other
SS is the sequence
number of the
account. Valid values
are ‘01’ through ‘99’.
A value of ‘01’
indicates that this is
the primary account
of the type indicated.
Processing Rules For processors supporting packed numeric fields: Because the
data for this transaction may exceed 255 bytes, if the numeric
packing option is enabled, the variable length indicator for DE 105
(for this transaction only) will be 2-byte binary rather than the
standard 1-byte binary.
The Data Detail segment can occur up to 12 times, totaling 516 bytes
maximum. For ABP transactions, at least one occurrence of the Detail
segment must follow the Fixed segment, beginning in position 3 of DE 105.
Because there may be multiple occurrences, the position numbers given
above are relative to the segment. The number of occurrences of the Detail
segment must match the value specified in the “Number of Items” field in the
Fixed segment. For requests to co-op processors, the Detail segment will
contain the account numbers and qualifiers of the accounts for which balances
are requested.
Acquirer / Issuer
■ ‘00’ or spaces =
text is not
supported
■ If the Issuer populates the Receipt Text Indicator, and does not
populate the new balance descriptor / amount fields, the
standard balances (from DE 054) are displayed.
Statement Processing
DE 121 for statement processing consists of segments that may or may not be
present based on message and/or statement request type. The Statement
Data Fixed Segment is required for statement request (0200) and reply
(0210) messages. The Statement Reply Fixed Segment is required for reply
messages. All other segments are conditional for reply messages only.
Acquirer/Issuer
Processing Rules ■ The original request indicates to the issuer the type of reply
data the acquirer supports.
Acquirer/Issuer
Values The Statement Data Fixed Segment must be echoed from the
request message (except the account number, which must be in
the reply from non-coop processors). The response data is broken
into several segments, some of which may be repeated. See
following sections for corresponding formats.
This segment is required in all Statement Request and Reply messages. All
subfields except Account Number must be echoed from the request to the
reply.
■ ‘301’ = Credit
■ ‘401’ = Other
■ ‘LAST’ = Issuer is
to reply with the
last “nn”
transactions
posted (positions
27-28).
27-28 Number of
transactions
requested (“nn”).
29 Space
30 Type of transaction
requested:
■ ‘A’ = All
transaction types
■ ‘M’ = MAC®/STAR
transactions only
■ ‘S’ = Spanish
■ ‘Y’ = Yes
■ ‘N’ = No
The Reply Fixed Segment is 11 bytes in length and provides basic information
about the message and its relationship to the entire reply. This segment
begins in position 33 of DE 121, following the 32-byte Statement Data Fixed
Segment. The position numbers given below are relative to the segment. The
subsequent segments present in the message must match the Statement
Composition indicator in position 11 of the Reply Fixed Segment.
◆ ‘H’ = Header
◆ ‘D’ = Detail
◆ ‘T’ = Trailer
The Detail Segment is 31 bytes, and holds the actual transaction data.
Multiple occurrences of the Detail Segment can appear in the data element of
a reply. The number of occurrences of the Detail Segment is indicated by the
Number of Items Here field (positions 9-10).
■ If numeric packing option is disabled, occurs up to 25 times (775 bytes
maximum)
■ If numeric packing option is enabled, occurs up to 6 times (186 bytes
maximum)
At least one occurrence of the 31-byte Detail Segment described below must
follow the reply’s fixed segment, beginning in position 44. Because there may
be several occurrences, the position numbers given below are relative to the
segment
The Detail Segment(s) must be sent in a separate message — they may not
be present in the same message with the Header or Trailer segments.
If Header and/or Trailer messages are included in the replies, then the Detail
message(s) must follow the Header message and precede the Trailer
message.
■ ‘DR’ = Debit
If a Header message is included it must be the first reply message sent. The
Header Segment(s) must be sent in a separate message — they may not be
present in the same message with the Trailer or Detail segments.
If a Trailer message is included it must be the last reply message sent. The
Trailer Segment(s) must be sent in a separate message — they may not be
present in the same message with Header or Detail segments.
Country/Currency/State Codes
Country/Currency Code
ESP 0
020 ADP 0
250 FRF 2
982 AOR 2
973 AOA 2
978 EUR 2
978 EUR 2
064 BTN 2
840 USD 2
983 ECV 2
840 USD 2
232 ERN 2
978 EUR 2
978 EUR 2
978 EUR 2
978 EUR 2
978 EUR 2
978 EUR 2
978 EUR 2
840 USD 2
978 EUR 2
978 EUR 2
426 LSL 2
978 EUR 2
978 EUR 2
978 EUR 2
978 EUR 2
978 EUR 2
840 USD 2
978 EUR 2
978 EUR 2
946 RON 2
643 RUB 2
Grenadines
978 EUR 2
978 EUR 2
978 EUR 2
891 YUM 2
State Codes
Table 16.2: State Codes
State Alpha Numeric
Alabama AL 01
Alaska AK 02
Arizona AZ 04
Arkansas AR 05
California CA 06
Colorado CO 08
Connecticut CT 09
Delaware DE 10
District of Colombia DC 11
Florida FL 12
Georgia GA 13
Hawaii HI 15
Idaho ID 16
Illinois IL 17
Indiana IN 18
Iowa IA 19
Kansas KS 20
Kentucky KY 21
Louisiana LA 22
Maine ME 23
Maryland MD 24
Massachusetts MA 25
Michigan MI 26
Minnesota MN 27
Mississippi MS 28
Missouri MO 29
Montana MT 30
Nebraska NE 31
Nevada NV 32
New Hampshire NH 33
New Jersey NJ 34
New Mexico NM 35
New York NY 36
North Carolina NC 37
North Dakota ND 38
Ohio OH 39
Oklahoma OK 40
Oregon OR 41
Pennsylvania PA 42
Rhode Island RI 44
South Carolina SC 45
South Dakota SD 46
Tennessee TN 47
Texas TX 48
Utah UT 49
Vermont VT 50
Virginia VA 51
Washington WA 53
West Virginia WV 54
Wisconsin WI 55
Wyoming WY 56