STAR ISO 8583 Message
Format Guide
February 2011
Version 3.3
Printed in U.S.A.
This document contains confidential and proprietary information of First
Data Corporation. You may not disclose, copy or use any portion of these
materials for any purpose without the express written consent of First
Data Corporation.
All trademarks, service marks, and trade names referenced in this
material are the property of their respective owners.
Periodic revisions to this manual are issued to reflect technical changes
and enhancements to the System, and to ensure that all information
contained herein remains current and accurate.
Revision Guide February 2011
Chapter Updated Description of Change
Chapter 1 Updated Introduction Chapter 3 Updated tables:
■ Table 3.11: 0100/0101 Pre-authorization Request ■ Table 3.12: 0110 Pre-authorization Response ■ Table 3.13: 0120/0121 Pre-authorization Advice ■ Table 3.15: 0200/0201 Financial Transaction Request ■ Table 3.16: 0210 Financial Transaction Response ■ Table 3.17: 0220/021 Financial Transaction Advice ■ Table 3.33: 0420/0421 Acquirer Reversal Advice
Chapter 4 Updated elements:
■ DE 042 Card Acceptor/Merchant Identification Code ■ DE 125 Network Management Information/Tagged Issuer
Data
Chapter 9 Updated Table 9.1: Valid Response Codes
■ Added ‘A1’, ‘A2’ and ‘S7’
Chapter 11 Updated Table 11.9: Position 9-10: Terminal Type Chapter 13 Updated Data Element 104: Transaction Description -
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
0312 Card Issuer File Update Response (Negative File) 90
0322 Negative File Update Advice 92
0332 Negative File Update Advice Acknowledgement 93
0382 PIN Change Request 93
0392 PIN Change Reply 95
0382 PIN Offset File Update Request 96
0392 PIN Offset File Update Reply 98
0382 Card Activation Request 100
0392 Card Activation Reply 100
0384 PIN Change Advice - NE Platform 102
0394 PIN Change Advice Acknowledgement - NE
Platform 102
Reversal Messages 104
0420/0421 Acquirer Reversal Advice 104
0430 Acquirer Reversal Response 112
Administrative Messages 114
0620 Administrative Advice 114
Network Management Messages 115
0800 Network Management Request 115
0810 Network Management Response 116
Chapter 4: Data Element Definitions 117
STAR ISO 8583 Message Data Formats 117
Unsupported Data Elements 117
Data Elements 119
Part 2: Reference Material 216
Chapter 5: Data Element Index 217
Data Element by Alphabetical Element Description 217
Chapter 6: Format Options 223
ASCII/EBCDIC Table 223
Check Digit Calculation 235
Modulus 10 Check-Digit Routine 235
Example 235
Luhn Formula 236
Example 236
Chapter 7: Data Element 003: Processing Codes 237
ATM 237
Mandatory (Issuer/Acquirer) 237
Optional (Issuer/Acquirer) 238
Point of Sale 240
Mandatory (Card-Issuer Processor Only) 240
Mandatory (Acquirer Only) 243
Optional 243
Chapter 8: Data Element 018: Merchant Type 244
Merchant Type Codes - Numerical Order 244
Merchant Type Codes - Alphabetical Order 276
Chapter 9: Data Element 039: Response Codes 310
Chapter 10: Data Element 054: Additional Amounts 317
Overview 317
Account Balance Handling 318
Partial Amount Authorization 318
STAR SE/W Platform 318
STAR NE Platform 319
Pre-authorized Amount Completion 320
Account Type 320
Amount Type 321
Currency Code 323
Amount 324
Chapter 11: Data Element 058: National Point of Service 325
DE 058 - Position 1: Terminal Operation 325
DE 058 - Position 2: Customer Operation 325
DE 058 - Position 3: On/Off Premise 325
DE 058 - Position 4: Cardholder Present 326
DE 058 - Position 5: Card Present 326
DE 058 – Position 6: Device Card Retention 327
DE 058 – Position 7: Transaction Disposition 327
DE 058 – Position 8: Security Condition 328
DE 058 – Position 9-10: Terminal Type 329
Sample STAR ISO Acquirer P-58 Combinations 331
Chapter 12: Data Element 060: Advice/Reversal Reason Code 334
Reversal Reason 334
Advice Reason 335
Chapter 13: Data Element 104: Transaction Description - Interchange
Group Identifier Values 337
Chapter 14: Data Element 105: Large Private Data 343
POS Payment Transactions 343
Account List Inquiry 344
Account Balance Profile 346
Enhanced Balance on Receipt 349
Chapter 15: Data Element 121: Additional Data, Private Issuer 352
Statement Processing 352
0200 Message Statement Data Request 352
121Additional Data, Private Issuer – Statement Data
Request 352
0210 Statement Data Reply Message 353
121Additional Data, Private Issuer – Statement Data
Reply 353
DE 121 – Statement Data Fixed Segment (32 Bytes) 354
DE 121 Reply Fixed Segment (11 Bytes) 357
DE 121 Reply Detail Segment (31 Bytes) 358
DE 121 Reply Header Segment (72 Bytes) 359
DE 121 Reply Trailer Segment (72 Bytes) 359
Chapter 16: Country/Currency/State Codes 360
Part 1: STAR ISO 8583 Message
Format Guide
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:
Manual Title
Description
STAR ISO 8583 Message Format Guide
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.
STAR ISO 8583 Gateway/ Product Interface Guide
The STAR ISO 8583 Gateway/Product Interface Guide provides additional processing information for
Gateway, Electronic Benefits Transfer, and STAR Product processing.
STAR Platform Interface Guide
The STAR Platform Interface Guide is the technical interface to the STARprocessing 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
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:
■
Transaction Amount
■Currency Information
■
Merchant Type Code
■Point of Service Information
■Convenience Fees (Surcharge and
Rebate)
■
Response Codes
■
Location Information
■Additional Amount Information
■Network Identifiers
■Merchant Authorized Transactions
■Merchant Authorized Submissions
and Resubmissions Processing
■
Matching POS Pre-authorization to
Financial Completions
■
Routebacks
■Over/Under Dispense Reversals
■Corrections/Cancellations
■STAR ISO Message Handling
■Repeat Transactions
Considerations
Transaction Amount
Fields DE 004 Amount, Transaction DE 005 Amount, Settlement DE 006 Amount, Cardholder Billing
Considerations ■When a STAR cardholder is performing an ATM or POS transaction in
a currency of other than US dollars, and if the acquiring network passes "multi-currency" fields in request messages, then DE 004 will contain the transaction amount in the acquirer's currency, and will contain the transaction amount in US dollars. Therefore, when both DE 004 and DE 005 are present in the transaction, DE 005 will contain the amount to be debited from or credited to the cardholder's account. Processors should consider making both fields available on the customer’s statement and reporting both amounts on internal/ settlement reports. Having both amounts available will aid in resolving consumer questions relating to international transactions.
■Because the STAR platform is settled in US dollars and currently all
STAR issuers are US-based issuers, DE 005 (Amount, Settlement) and DE 006 (Amount, Cardholder Billing) for non-US dollar transactions are always equal. When they are equal DE 006 is by default suppressed.
■For MasterCard transactions that include a currency conversion
assessment (CCA) fee, DE 005 contains the sum of the transaction amount and the CCA. STAR issuers on the SE/W Platform have an option to be passed DE 006 - which will contain the transaction amount without the CCA fee. STAR issuers on all STAR platforms receive (or have the option to receive) the CCA fee in DE 055. For transactions involving CCA, the amount in DE 006 + DE 055 = DE 005.
■When a cardholder of a non-US-based issuer uses a STAR ATM or POS
device, and the issuing network passes "multi-currency" fields in response messages, then the STAR ISO acquirer may receive DE 006 (Amount, Cardholder Billing) in the response message. The STAR terminal owner is not required to retain this field.
■See also Chapter 16 in this manual and the STAR ISO 8583 Gateway/
Currency Information
Fields DE 009 Conversion Rate, Settlement DE 010 Conversion Rate, Cardholder Billing DE 016 Date, Conversion
DE 019 Acquiring Institution Country Code DE 049 Currency Code, Transaction DE 050 Currency Code, Settlement DE 051 Currency Code, Cardholder Billing DE 114 Country Code, Authorizing Agent
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.
■Other networks to which a STAR network is connected (e.g., CIRRUS
and PLUS) support international transactions. Therefore, the currency information can be valuable for participants of the international networks.
For example, if a STAR cardholder used an ATM in Europe, the STAR ISO request message would provide information about the type of currency which was dispensed, the country in which the terminal was located, the date of the currency conversion, and the rate at which the currency was converted to US dollars. If the cardholder later questioned the transaction, the issuing institution, which retains the currency information, would be able to relay the pertinent information to the cardholder.
■The Acquirer Institution Country Code would be valuable to business/
marketing areas to determine where their customers are traveling to outside of the US.
Merchant Type Code
Fields DE 018 Merchant Type
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.
Point of Service Information
Fields DE 022 Point-Of-Service Entry Mode DE 025 Point-Of-Service Condition Code
DE 058 National Point-Of-Service Condition Code
Considerations ■DE 022 must be present for all POS transactions, and is optional (but
recommended) for ATM transactions.
■DE 058 must be present for all transactions.
■Special transaction processing might also be necessary, depending
upon the content in these fields. For example, the Card-Issuer Processor might want to perform special processing on a merchant authorized resubmission transaction. The Card-Issuer Processor might also use the terminal type code to determine what type of fees (if any) are to be charged to the customer.
■DE 025 Point-Of-Service Condition Code is optionally used/available
on the STAR SE/W platforms. It may only be sent/received to supplement the information in DE 058. It may not be used without DE 058. When DE 025 is sent to STAR issuers, it will generally contain information that was received from other networks (e.g., Visa) behind STAR‘s.
Convenience Fees (Surcharge and Rebate)
Fields DE 028 Amount, Transaction Fee DE 029 Amount, Settlement Fee
Considerations ■The STAR network allows surcharging or rebating of transactions by
terminal owners. The amount of the transaction must be reported separately from the amount of any surcharge/rebate in the online transaction.
■Note that when STAR cardholders are performing transactions in a
non-US currency, and a surcharge is being assessed, the surcharge amount in DE 028 will be in the acquirer's currency, and in DE 029 in US currency. Therefore, when both DE 028 and DE 029 are present in the request message, the issuer processor must use the amount from DE 029 for posting the fee to the cardholder's account.
■The Card-Issuer Processor has new options relating to the handling of
surcharge/rebates. First, the Card-Issuer Processor can now exclude the surcharge/rebate amount when checking the cardholder limits (thereby avoiding the problem of customers requesting their full limit being denied for over-limit because the Acquirer Processor added a surcharge). Secondly, the Card-Issuer Processor can report the transaction amount separately from the surcharge/rebate amount on the customer's statement.
Response Codes
Fields DE 039 Response Code
Considerations A Card-Issuer Processor must support a minimum set of response codes. The remaining codes can be optionally supported by the
Card-Issuer Processor. STAR ISO Acquirer Processors must ensure they map all of the response code values to existing terminal screens, or have created new screens to support the codes. Acquirer Processors that track response codes for reporting purposes must take into account all response codes and make modifications where necessary.
Location Information
Fields DE 043 Card Acceptor Location
DE 048 Member Institution/Merchant Name
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.
Additional Amount Information
Fields DE 054 Additional Amounts
Considerations As STAR network transaction processing options continue to increase in number, the usages of DE 054 likewise increase. See Chapter 4 and Chapter 10 of this guide for additional details.
Network Identifiers
Fields DE 063 STAR Identification Data
Considerations ■For transactions involving an acquiring or issuing network of other
than STAR, DE 063 is used to convey a three-position alphanumeric acquirer or network "network ID" to identify the other network.
■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 /
Merchant Authorized Transactions
Considerations Merchants or Merchant Processors may authorize transactions on behalf of the Card-Issuer Processor under two varying scenarios:
◆ Scenario 1: The Merchant Processor connection to the network is
unavailable and cannot receive an authorization or denial response for a transaction (this is commonly referred to as “Merchant Store & Forward”).
◆ Scenario 2: The Merchant or Merchant Processor receives a denial
from the Card-Issuer Processor for Insufficient Funds (response code ‘51’) or Exceeds Limit (response codes ‘61’, ‘65’), and chooses to over-ride the denial from the Card-Issuer Processor and approve the transaction for the customer.
Merchant Authorized Transactions, other than pre-authorized completion transactions meeting the requirements in the Operating Rules, are at the risk of the Merchant. The STAR Switch shall neither authorize nor decline Merchant Authorized Transactions on behalf of the Processor. If the Card-Issuer Processor is unavailable to authorize or decline a Merchant Authorized Transaction, the Switch shall deny the transaction as “Issuer Inoperative” to the Merchant or Merchant Processor.
Valid response codes for Resubmission of Merchant Authorized Transactions Scenario #1 (Merchant Store & Forward)
Response Code ‘51’ ‘55’ ‘61’ ‘65’ ‘75’ ‘76’ Description
Not Sufficient Funds Invalid/Incorrect PIN
Exceeds Withdrawal Amount Limit Exceeds Withdrawal Frequency Limit Allowable PIN Tries Exceeded Key Sync Error
Valid response codes for Resubmission of Merchant Authorized Transactions Scenario #2: Response Code ‘51’ ‘61’ ‘65’ Description
Not Sufficient Funds
Exceeds Withdrawal Amount Limit Exceeds Withdrawal Frequency Limit
Merchant Authorized Submissions and Resubmissions Processing
Considerations ■The initial submission of a Merchant Authorized Transaction is
referred to as an 'Original Submission'. Subsequent submissions of a Merchant Authorized Transaction, following a denial of the Original Submission, are referred to as a 'Resubmission'.
■An Original Submission may be sent to the STAR Switch once, except
when it is denied by the STAR Switch for 'Issuer Inoperative'. Original Submissions denied by the STAR Switch for 'Issuer Inoperative' may be re-sent to the network Switch once every 30 minutes until an approval or denial (other than Issuer Inoperative) is received.
■Data Elements for submission and resubmission transactions:
DE 002 PAN (required if DE 035 is not provided) DE 013 Local Date (date transaction occurred). DE 022 Point of Service Entry Mode
◆ Set to ‘021’ on Submission (with Track and PIN) ◆ Set to ‘022’ on Resubmission (with Track and
without PIN)
◆ Set to ‘012’ on Resubmission (without Track and
without PIN)
DE 035 Track 2 Data on submissions (optional on resubmissions)
DE 052 PIN Data on submissions (not present on resubmissions)
■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.
■Resubmissions can be transmitted only one time during a 24-hour
period during a 12-day time frame.
■In addition, the National Point of Service Condition Code must be
updated.
■Position 7 should be set to 4 on all initial submission transactions. All
resubmissions should be set to 5.
■All additional information contained in DE 058 should remain the
same throughout the Life of the Transaction.a
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
Considerations ■Following receipt of a POS transaction, any correction or cancellation
of the amount of the transaction must be initiated by swiping the magnetic stripe on the card and entering the PIN. The correction or cancellation may be for all or part of the original transaction amount and must be initiated within 24 hours of the original transaction.
■STAR Acquirer Processors imposing a Convenience fee (surcharge) on
the original transaction must separate the surcharge amount in the correction/cancellation transaction. The surcharge amount is contained in Amount, Transaction Fee (DE 028).
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.
Platform Distinction
The STAR NE Platform does not support this option.
Over/Under Dispense Reversals
Fields DE 095 Replacement Amounts DE 056 Replacement, Additional Fees
Considerations ■Over- and under-dispense reversals are supported via an 0420
message, not as an additional debit transaction.
■DE 095 should be populated with the amount actually dispensed
(e.g., an amount greater or less than the original amount requested).
■DE 095 should not be populated with amount equal to the original
amount in DE 004 or DE 005, because if the amount dispensed equaled the amount requested, then reversal would have no net effect.
■Zero-dollar reversals (where the amount in DE 004 or DE 005 is zero)
are not permitted.
■Transactions that include a MasterCard Currency Conversion
Assessment (CCA) fee and are reversed for an over- or
under-dispense, will include DE 056 to convey the replacement CCA fee.
■Please see Chapter 4 of this guide and the STAR ISO Gateway /
Matching POS Pre-authorization to Financial Completions
Fields DE 038 Authorization Identification Response
Considerations ■For signature debit POS transactions, the following matching criteria
are recommended:
◆ DE 002 (or DE 035 or DE 045) – Primary Account Number (PAN) ◆ DE 038 – Authorization ID; DE 038 is provided by the Card Issuer in
the pre-authorization response and is returned in the financial completion.
■Additional matching criteria that can be used for secondary matching
include:
◆ DE 004 – Transaction Amount (+/- 20 –25%) ◆ DE 013 – Local Date
◆ DE 018 – Merchant Type (Merchant Category Code or SIC) ◆ DE 127 – Pre-authorization Key (assigned by Visa / MasterCard) Platform
Distinction
The following criteria are recommended for matching PIN-based POS pre-authorizations to completions on different STAR platforms.
■On the STAR SE/W Platforms:
◆ DE 002 PAN (in completions) with PAN portion of DE 035 Track 2 ◆ DE 011 – System Trace Audit Number
◆ DE 041 – Card Acceptor Terminal Identification ■On the STAR NE Platform:
◆ DE 002 PAN (in completions) with PAN portion of DE 035 Track 2 ◆ DE 011 – System Trace Audit Number
◆ DE 035 – Card Number
◆ DE 013 – Local Transaction Date ◆ DE 012 – Local Transaction Time
STAR ISO Message Handling
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
Platform Distinction
■ On the STAR SE/W platforms, if an acquirer is sending a repeat
message, fields and content must be the same between the original and the repeat message (except for the message type identifier, which increases by one). For example, a repeat message for a 0100 Pre-authorization Request could have a message type identifier of 0101.
■If the STAR NE Platform receives a repeat transaction from an
Acquirer, the Switch will format this transaction into the original message type. For example, a 0201 will be received by the STAR NE Switch and formatted into a 0200.
■If the STAR SE/W platform sends a 0220 or 0420 advice to an issuer
and does not receive a timely 0230 or 0430 acknowledgement, then the same advice will be resent using a message type of 0221 or 0421 until an acknowledgement is received.
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
Whenever a repeat message is identified, the repeat message must be the
same as the original message, except for the Message Type identifier, which
increases by one. For example, the repeat of a 0100 Pre-authorization
Request message would have a Message Type identifier of 0101.
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
Pre-authorizations occur in both PIN-based and signature debit POS
transactions as the first part of a two-part POS transaction. A
pre-authorization is used to validate if the cardholder has sufficient funds for a
point-of-sale purchase. The transaction, produced at the time of the purchase,
represents the amount to hold on the cardholder account.
■
All issuing Point of Sale processors must certify this message type.
■Optional for Point of Sale Acquirer Processors.
■
On the STAR SE/W Platforms, Acquirer Processors who do not receive a
0110 reply after 60 seconds may optionally generate a 0101 repeat
request transaction.
■
STAR Card-Issuer Processors must be able to accept both 0100 requests
and 0101 repeat request message types. Similarly, they must be able to
accept both 0120 and 0121 advice messages. The 0120/0121 advices will
be retransmitted to a Card-Issuer Processor once each minute until a
matching 0130 is received. If a Card-Issuer Processor is unavailable when
an 0120 is generated, the message will be saved and attempts at
transmission will begin when communications have been reestablished.
■It is highly recommended that the STAR network’s interleaving option be
used to efficiently manage stand-in and advice notification. This feature
allows those processors that have developed a large store-and-forward
queue file the ability to intermingle received online with advice transaction
activity.
■
If a STAR processor receives invalid data element content in a
pre-authorization request or an advice message, then STAR processing will
deny the transaction in the 0110/0130 response message back to the
acquirer using Response Code 30 (format error) and will include the data
element number that is in error within DE 044.
■
If the Issuer receives invalid data element content in a pre-authorization
request message, then the Issuer should deny the transaction in the 0110
response message using Response Code 30 (format error) and should
include the data element number that is in error within DE 044. STAR
Issuers receiving invalid data element content in an advice message must
still acknowledge the message with a 0130 message with a Response Code
00 (approved).
■
If STAR processing receives a pre-authorization request or advice for
which it is unable to parse bit or byte maps or field lengths, then STAR
Networks will return a 0620 message to the acquirer.
■
STAR Issuers should only send a 0620 message in response to a 0100 or
0200 request if they are unable to parse the bit or byte maps or the field
lengths.
■
Similarly, STAR Acquirers should only send a 0620 message in response to
a 0110 or 0210 response if they are unable to parse the bit or byte maps
or the field lengths.
Table 3.1:
Pre-authorization Message Types
Type ID Message Type Comments
0100 Pre-authorization Request
Both PIN-based and signature debit transactions.
0101 Repeat Pre-authorization Request
STAR SE/W Platforms only.
0110 Pre-authorization Reply To ensure appropriate matching criteria, DE 038, Authorization ID is provided by the Issuer. This information is provided in the inbound completion.
0120 Pre-authorization Advice
0121 Repeat Pre-authorization Advice
STAR SE/W Platforms only.
0130 Advice
Financial Transaction Messages
Disposition: Financial (Settled Transactions)
Financial transaction messages transport ATM and POS transactions
generated by cardholders using their access cards at terminals driven by an
Acquirer Processor connected to the STAR Switch.
■
Required for all ATM and POS Card-Issuer Processors.
■
On the STAR SE/W Platforms, Acquirer Processors who do not receive a
0210 reply after 60 seconds may optionally generate a 0201 repeat
request transaction.
■
STAR Card-Issuer Processors must be able to accept both 0200 requests
and 0201 repeat request message types. Similarly, they must be able to
accept both 0220 and 0221 advice messages. The 0220/0221 advices will
be retransmitted to a Card-Issuer Processor once each minute until a
matching 0230 is received. If a Card-Issuer Processor is unavailable when
a 0220 is generated, the message will be saved and attempts at
transmission will begin when communications have been reestablished.
■It is highly recommended that STAR's interleaving option be used to
efficiently manage stand-in and advice notification. This feature allows
those processors that have developed a large store-and-forward queue file
the ability to intermingle received online with advice transaction activity.
■If STAR processing receives invalid data element content in a financial
request or advice message, then the STAR processor will deny the
transaction in the 0210/0230 response message back to the acquirer using
Response Code 30 (format error) and will include the data element number
that is in error within DE 044.
■
If the Issuer receives invalid data element content in a financial request
message then the Issuer should deny the transaction in the 0210 response
message using Response Code 30 (format error) and should include the
data element number that is in error within DE 044.
■
Issuers receiving invalid data element content in an advice message must
still acknowledge the message with a 0230 with a Response Code 00
(approved).
■
If STAR receives a financial request or advice for which it is unable to parse
bit or byte maps or field lengths, then STAR Network will return a 0620
message to the acquirer.
■
STAR Issuers should only send a 0620 message in response to a 0100 or
0200 request if they are unable to parse the bit or byte maps or the field
lengths.
■
Similarly, STAR Acquirers should only send a 0620 message in response to
a 0110 or 0210 response if they are unable to parse the bit or byte maps
or the field lengths.
File Maintenance Messages
Disposition: Administrative
The Negative File Maintenance message provides the Card-Issuer Processor
with the ability to maintain the STAR Negative File online. When
communication is lost between the Card-Issuer Processor and the STAR
Switch, the negative file is checked by the STAR Switch as part of the
authorization process in stand-in.
The PIN Change File Maintenance messages provides the Card-Issuer
Processor with the ability to send or receive PIN change and PIN offset
maintenance transactions online.
Table 3.2:
Financial Transaction Message Types
Type ID Message Type Comments
0200 Financial Request ■ ATM, POS, Point of Banking transactions.
■ Data Element DE 003 (Processing Code) defines the
type of financial requested.
0201 Repeat Financial Request
STAR SE/W Platforms only.
0210 Financial Reply
0220 Financial Advice ■ Forced post transaction by the merchant acquirer. ■ Stand-in financial transaction approved by the STAR
Switch.
0221 Repeat Financial Advice STAR SE/W Platforms only.
0230 Financial
The STAR NE Platform provides an optional service to notify an Issuer online
when updates have been made to their card data. With this option, Issuers
can receive an 0302 or a 0322 and respond back with a 0312 or 0332 to
ensure that their own internal negative file is synchronized.
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.
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.
Table 3.3:
File Maintenance Message Types
Type ID Message Type Comments
0300 Acquirer File Update Request
■ Normally, an Issuer-initiated request.
■ 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 0300 would be sent to the Issuer.
0302 Negative File Update Request
■ Normally, an Issuer-initiated request. ■ 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 0302 would be sent to the Issuer.
■ 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.
0310 Acquirer File Update Response
■ Normally, a STAR processor response to the Issuer. ■ 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 Reply
■ Normally, a STAR processor response to the Issuer. ■ 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.
0322 Negative File Update Advice
■ A STAR processing response to the Issuer. ■ 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 0322 would be sent to the Issuer from STAR.
■ 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.
0332 Negative File Update Advice
Acknowledgement
■ Normally, a STAR processor response to the Issuer. ■ 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.
0382 PIN Change Request A STAR processing initiated request.
0392 PIN Change Reply An Issuer response to a STAR initiated PIN change request.
0382 PIN Offset File Update Request
An Issuer initiated request.
Table 3.3:
File Maintenance Message Types (cont.)
Card Activation Messages
Disposition: CMA Card Activation
The STAR NE Platform provides an optional online service to notify an Issuer
whenever a card has been activated. Once an Issuer establishes the option to
receive a Card Activation Notification message, whenever a card has been
activated through a pinned transaction (ATM or POS), VRU Activation,
Cardholder Maintenance File (CMF), or STAR STATION CMA Activation entry,
CMA will forward a 382 Card Activation Notification message to the Issuer.
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
Disposition: Financial or Non-financial (reflecting the original
transaction)
A reversal is an electronic message, generated by the Acquirer or the STAR
Switch, that serves to cancel all or part of a previously authorized STAR
transaction. A reversal may not be processed as instructed for the reasons
listed below:
■
The message cannot be delivered.
■The message cannot be processed.
■
The message has been cancelled by the receiver.
Reversals have the following stipulations:
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 Reply
A STAR processing response to the Issuer.
0394 PIN Change Advice Acknowledgement
STAR NE: An issuer acknowledgement of a STAR initiated PIN change advice.
Table 3.3:
File Maintenance Message Types (cont.)
■
This transaction is required for all issuing and acquiring ATM/POS
processors.
■
This transaction will be accepted as a reversal of an approved 0110 or
0210 transaction.
■
Reversals of approved balance inquiry transactions are not supported.
■On the STAR SE/W Platforms, Acquirer Processors who do not receive a
0430 reply after 60 seconds may optionally generate a 0421 repeat
reversal transaction.
■
STAR Card-Issuer Processors must be able to accept both 0420 reversal
and 0421 repeat reversal message types. The 0420/0421 reversals will be
retransmitted to a Card-Issuer Processor once each minute until a
matching 0430 is received. If a Card-Issuer Processor is unavailable when
a 0420 is generated, the message will be saved and attempts at
transmission will begin when communications have been reestablished.
■It is highly recommended that the STAR network’s interleaving option be
used to efficiently manage stand-in and advice notification. This feature
allows those processors that have developed a large store-and-forward
queue file the ability to intermingle received online with advice transaction
activity.
■
If STAR processing receives invalid data element content in a reversal
messages, then STAR will acknowledge the message with a 0430 response
message back to the acquirer using Response Code 30 (format error) and
will include the data element number that is in error within DE 044.
■
STAR Issuers receiving invalid data element content in a reversal message
must still acknowledge the message with a 0430 with a Response Code 00
(approved).
■
If a STAR processor receives a reversal for which it is unable to parse bit or
byte maps or field lengths, then STAR will return a 0620 message to the
acquirer.
■
If the STAR Issuer receives a reversal message for which it is unable to
parse bit or byte maps of field lengths, then the Issuer must minimally
return a protocol-level 'ACK'.
Table 3.4:
Reversal Message Types
Type ID Message Type Comments
0420 Reversal Advice DE 090, Original Data Elements provides information on the original transaction.
0430 Reversal Advice Acknowledgement
Table 3.4:
Reversal Message Types (cont.)
Administrative “Error” Messages
Disposition: Administrative
Administrative messages pass system-related information between the STAR
Switch and the Acquirer Processor or Card-Issuer Processor. They are used to
indicate that the STAR Switch was unable to parse a message or that a
mandatory data element is missing.
■
The STAR Switch will generate a 0620 Administrative Advice when the
Switch cannot successfully parse the bit or byte maps. A 0620 message
will also be generated if the processor fails to include the “mandatory”
fields in the message.
■
The additional data field will contain the first 255 bytes of the message in
error. Processors should log the receipt of a 0620 message from the
Switch for research purposes. In addition, processors should log an error
message to their network console indicating that an error condition has
occurred.
■
If the Issuer receives invalid content in one or more data elements in a
request message, then the Issuer should deny the transaction in the 0110/
0210 response message using Response Code 30 (format error) and
should include the data element number that is in error within DE 044. If
the Issuer receives invalid content in data elements in a reversal or an
advice message, the Issuer must still acknowledge the message with a
0130/0230/0430 with a Response Code 00 (approved). It is not
appropriate to send a 0620 message (or a Response Code 30 reply) in
these situations.
■
Transactions responded to with a 0620 message will not have a reply or be
settled by the Switch.
■
STAR Issuers should only send a 0620 message in response to a 0100 or
0200 request if they are unable to parse the bit or byte maps or the field
lengths.
■
If the Issuer receives invalid content in one or more data elements in a
request message, then the Issuer should deny the transaction in the 0110/
0210 response message using Response Code 30 (format error). If the
Issuer receives invalid content in data elements in a reversal or an advice
message, the Issuer must still acknowledge the message with a 0130/
0230/0430 with a Response Code 00 (approved). It is not appropriate to
send 0620 messages in these situations.
Network Management Messages
Disposition: Administrative
Network Management messages are used to coordinate system or network
events or tasks and to communicate network status conditions.
■
All STAR Card-Issuer Processors and Acquirer Processors must certify the
0800 messages.
■
For Key Management Support, the STAR Switch maintains both the current
and prior values of the Acquirer Processor working key. If a transaction
received from an Acquirer Processor is subsequently denied by the STAR
security module for a key sync or sanity error, the Switch will attempt to
translate the PIN one additional time using the prior key.
When a key change message sent to a processor is rejected or not
responded to, the Switch will continue to encrypt the PIN using the
existing working key.
■
STAR strongly recommends that all processors maintain both the current
and prior working key values for translation purposes. Under this
methodology, processors should be able to avoid unnecessary key sync or
sanity errors due to key change situations.
Table 3.5:
Administrative “Error” Message Type
Type ID Message Type Comments
0620 Administrative Advice
Table 3.6:
Network Management Message Types
Type ID Message Type Comments
0800 Network Management Request
DE 070, Network Management Information Code is used to describe a specific purpose or function of each message.
0810 Network Management Response
Bit Maps and Data Elements
Immediately following the Message Type identifier, a message has at least
one “bit map” that is used to indicate which fields are present in the message.
The bit maps contain a series of 64 bits used to identify the presence or
absence of the data elements that are possible for that Message Type.
These 64 bit positions are represented as either:
■
16 hexadecimal bytes (if packing of bit maps is not being used)
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.
Table 3.7:
Message Bit Maps
Bit Map Description
Primary Present in all Message Types
◆Contains 64 bit positions to represent data elements 001–064. Secondary Present in messages containing data elements above 064
◆Contains 64 bit positions to represent data elements 065–128. ◆If Secondary bit map is present, first position is ‘1’.
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
Bit Number and ISO Field (Data Element) Name
The number in the Bit column is a key to finding a complete description of a
data element in
Chapter 4: Data Element Definitions
.
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:
Table 3.8:
Data Type Indicators
Indicator Definition Notes
b Binary – will be hexadecimal characters if the packing option is not set.
Left-justified with trailing zeros.
A Alphabetic characters only. Left-justified with trailing spaces.
N Numeric values (digits) only. Right-justified with leading zeros.
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.
ANS Alphabetic, numeric and special characters. Left-justified with trailing spaces.
NS Numeric and special characters. Left-justified with trailing spaces.
NP Numeric data element that is capable of being packed, based on the database setting. The data element contains numeric digits in unsigned packed format (4-bit BCD) when the numeric packing option is set. The associated number indicates the number of digits the data element contains.
When the numeric packing option is set, all lengths are 1-byte binary. Odd-length packed numerics have a leading zero to ensure that data elements begin and end on byte boundaries.
LLV ■Variable data field that can have a length
range of 1-99.
■When the packing option is not set, the
variable-length subfield is 2 numeric characters long. Otherwise, the
variable-length subfield is one byte long.
■The maximum data element
length that can be represented by the packed 1-byte binary is 255.
■The length of a variable-length
field may exceed the maximum message size defined by STAR‘s software. If this occurs, only the message size defined by STAR will pass through the Switch.
LLLV ■Variable data field that can have a length
range of 1-255.
■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.
X ■‘C’ indicates a positive amount (credit). ■‘D’ indicates a negative amount (debit). ■For zero amounts, ‘0’ may be used.
For financial transactions, the value of the amount (credit or debit) is given from the cardholder’s perspective.
Table 3.8:
Data Type Indicators (cont.)
Requirements – Trnsmit / Recv
The Trnsmit (Transmit) and Recv (Receive) columns contain indicators of
whether individual data elements within a message are always, sometimes, or
never required:
The data elements defined by STAR as conditional or optional may be required
to interchange with endpoints using other message structures. Refer to the
STAR ISO 8583 Gateway/Product Interface Guide for the specific link to
determine additional data element requirements.
Table 3.9:
Requirements Indicators
Indicator Description
M Mandatory – The data element must be present in the message. Issuers/ Acquirers should populate their messages and/or edit accordingly.
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. The data element is not present for this message instance.
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.
Table 3.10:
Format Abbreviations and Common Notes
Notes Description MM Month (01-12) DD Day (01-31) YY Year (00-99) hh Hour (00-23) mm Minute (00-59) ss Second (00-59) Multi-Currency Field
Field may be present when the transaction involves more than one currency. Specifically, additional fields may be passed when the local (acquiring) currency, the switch settlement currency (US dollars), and the cardholder currency are not all the same.
Pre-authorization Messages
0100/0101 Pre-authorization Request
Table 3.11:
0100/0101 Pre-authorization Request
Requirements
Bit ISO Field Name Data Type Trnsmit Recv Notes
– Message Type N4 M M ■Always ‘0100’ initially. ■‘0101’ if repeated by
Acquirer. – Bit Map, Primary b64 M M
001 Bit Map, Secondary b64 C C Required if fields are specified in DE 065 to DE 128. 002 Primary Account Number LLV N19 C C ■Required if PAN is manually entered. ■If electronically captured, DE 035 or DE 045 must be present. 003 Processing Code N6 M M 004 Amount, Transaction N12 M M
005 Amount, Settlement N12 C C Multi-Currency Field 006 Amount, Cardholder
Billing
N12 C C Multi-Currency Field
007 Transmission Date & Time
N10 M M ■Updated by each
processing end point.
■Greenwich Mean Time. ■MMDDhhmmss 008 Amount, Cardholder Billing Fee N8 O O Unsupported 009 Conversion Rate, Settlement N8 C C Multi-Currency Field 010 Conversion Rate, Cardholder Billing N8 C C Multi-Currency Field
011 System Trace Audit Number
N6 M M
012 Time, Local Transaction N6 M M hhmmss 013 Date, Local Transaction N4 M M MMDD
014 Date, Expiration N4 O O ■Signature debit if Track
1 or 2 data is not available.
■YYMM
015 Date, Settlement N4 M M ■STAR business date. ■MMDD
016 Date, Conversion N4 C C ■Multi-Currency Field. ■Return if available. ■MMDD 017 Date, Capture N4 O O MMDD 018 Merchant Type N4 M C 019 Acquiring Institution Country Code N3 C C 022 Point-Of-Service Entry Mode N3 M C
023 Card Sequence Number N3 O C 025 Point-Of-Service
Condition Code
N2 O O ■Present if sent by
another network.
■See the STAR ISO
8583 Gateway/Product Interface Guide. 026 Point-Of-Service PIN Capture Code N2 O C 027 Authorization Identification Response Length N1 O C
Table 3.11:
0100/0101 Pre-authorization Request (cont.)
Requirements
028 Amount, Transaction Fee
X + N8 O O
029 Amount, Settlement Fee X + N8 O O
030 Amount, Processing Fee X + N8 O O Unsupported 031 Amount, Settlement Processing Fee X + N8 O O Unsupported 032 Acquiring Institution Identification Code LLV N11 M M
033 Sponsor ID LLV N11 C ■Required in ATM
transactions if terminal is sponsored by a STAR financial institution. ■Applicable only on Acquirer side. 035 Track 2 LLV NS37 C C If electronically captured, DE 035 (or DE 045 from non-STAR Acquirers) must be present. 037 Retrieval Reference Number AN12 M M
040 Service Restriction Code AN3 O O Unsupported 041 Card Acceptor Term
Identification
AN8 M M
042 Card Acceptor Identification Code
ANS15 O C Required for STAR POS Acquirers.
043 Card Acceptor Location AN40 M C Sent, if available. Reg. E data required for STAR Acquirer Processors.
Table 3.11:
0100/0101 Pre-authorization Request (cont.)
Requirements
045 Track 1 LLV ANS76 C ■Present if sent by
another network.
■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.
■See STAR ISO 8583
Gateway/Product Interface Guide. 047 Additional Data, National LLLV ANS..100 C Electronic Commerce Indicators & UCAF data. 048 Merchant/Bank Name LLLV
ANS025
M C Reg. E Data required for all STAR Acquirer Processors. 049 Currency Code, Transaction N3 M M ‘840’ = US 050 Currency Code, Settlement N3 C C Multi-Currency Field 051 Currency Code, Cardholder Billing N3 C C Multi-Currency Field 052 PIN Data b64 C C 054 Additional Amounts LLLV ANS120 O O 057 Authorization Life LLLV N003 M M 058 National Point-Of-Service Condition Code LLLV N010 M M 059 National Point-Of-Service Geographic Data LLLV AN017
O O Not required by the STAR network, but may be required by
Table 3.11:
0100/0101 Pre-authorization Request (cont.)
Requirements
061 Acquirer Transport Data LLLV ANS100
O O Will be echoed in response, but not forwarded to Issuer. 063 STAR Data LLLV
ANS050
M M
■ Byte Map AN2 M M Required to indicate the
presence of the subfields. Must be first subfield.
■ Pseudo Term AN6 M M Mandatory for STAR
Acquirers. ■ Issuer Network Identification AN3 O C ■ Acquirer Network Identification AN3 O C
■ Processor ID AN6 O M Switch-filled
067 Extended Payment Code N2 O O Unsupported
102 Account LLV ANS28 C C Used for Co-op Issuers (STAR NE Platform only). 103 Account Identification 2 LLV ANS28 O O Unsupported
104 Interchange Group Identifier
LLLV ANS100
C C ■Required for POS
Acquirer Processors.
■Also see Chapter 13 in
this manual.
Table 3.11:
0100/0101 Pre-authorization Request (cont.)
Requirements
111 Additional Data, Private Acquirer
LLLV AN255
O O ■SE/W platforms only. ■May be returned, if
received in the request, if the
Card-Issuer Processor desires to have this field returned in a reversal.
■See Chapter 8 in the
STAR ISO 8583 Gateway/Product Interface Guide. 113 Card Issuer Identification Code LLLV N011 O O 120 Account Qualifiers LLLV AN006 O C 122 Sponsor Bank ID LLLV AN011
O ■SE/W platforms only. ■If sent by another
network, this field is optionally available to STAR Issuers.
■STAR Acquirers should
not send in this field for ATM transactions.
■See Chapter 2 in the
STAR ISO 8583 Gateway/Product Interface Guide.
Table 3.11:
0100/0101 Pre-authorization Request (cont.)
Requirements
123 AVS / CVx2 / 3-D / Check Auth / ATM Overdraft / Cash/Check Deposits
LLLV ANS255
C C ■See Chapter 6 in the
STAR ISO 8583 Gateway/Product Interface Guide. ■Only present if required by or transmitted from another network.
■MICR data sent only if
available. 125 Network Management Information/Tagged Issuer Data LLLV ANS56
O O ■For Issuers that elect
to receive the ALL STAR Indicator 127 Acquirer Trace Data LLLV
ANS100
O O ■Only present if
required by or transmitted from another network.
■Details are available in
the STAR ISO 8583 Gateway/Product Interface Guide.
Table 3.11:
0100/0101 Pre-authorization Request (cont.)
Requirements
0110 Pre-authorization Response
Table 3.12:
0110 Pre-authorization Response
Requirements
Bit ISO Field Name Data Type Trnsmit Recv Notes
– Message Type N4 M M Always ‘0110’. – Bit Map, Primary b64 M M
001 Bit Map, Secondary b64 M M Required if fields specified in DE 065 to DE 128. 002 Primary Account Number LLV N19 C C Required, if received in 010x message. 003 Processing Code N6 M M
004 Amount, Transaction N12 M M Copied from the 010x message.
005 Amount, Settlement N12 C C Multi-Currency Field 006 Amount, Cardholder N12 C C Multi-Currency Field 007 Transmission Date &
Time
N10 M M ■Updated by each
processing end point.
■Greenwich Mean Time. ■MMDDhhmmss 008 Amount, Cardholder Billing Fee N8 O O Unsupported 009 Conversion Rate, Settlement N8 C C Multi-Currency Field 010 Conversion Rate, Cardholder Billing N8 C C Multi-Currency Field
011 System Trace Audit Number
N6 M M Copied from the 010x message.
012 Time, Local Transaction N6 M M ■Copied from the 010x
message.
013 Date, Local Transaction N4 M M ■Copied from the 010x
message.
■MMDD
014 Date, Expiration N4 O O ■May be returned, if
received in the request, if the
Card-Issuer Processor desires to have this field returned in a reversal.
■YYMM
015 Date, Settlement N4 M M ■STAR business date. ■MMDD
016 Date, Conversion N4 C C ■Multi-Currency Field ■Return if available. ■MMDD
017 Date, Capture N4 O O MMDD
018 Merchant Type N4 O C May be returned, if received in the request, if the Card-Issuer Processor desires to have this field returned in a reversal. 019 Acquiring Institution Country Code N3 O C 022 Point-Of-Service Entry Mode N3 O C
023 Card Sequence Number N3 O C 025 Point-Of-Service Condition Code N2 O O 028 Amount, Transaction Fee X + N8 O O
Table 3.12:
0110 Pre-authorization Response (cont.)
Requirements
029 Amount, Settlement Fee X + N8 O O
030 Amount, Processing Fee X + N8 O O Unsupported 031 Amount, Settlement
Processing Fee
X + N8 O O Unsupported
032 Acquiring Institution Identification Code
LLV N11 M M Copied from the 010x message.
033 Sponsor ID LLV N11 C Echoed only if sent by the Acquirer.
035 Track 2 LLV NS37 C C Required if received in 010x message.
037 Retrieval Reference Number
AN12 M M Copied from the 010x message.
038 Authorization
Identification Response
AN6 O C Required for
participation in some links.
039 Response Code AN2 M M If the response code is 30, then Additional Response Data (DE 044) contains the data element number in error. 040 Service Restriction Code AN3 O O Unsupported
041 Card Acceptor Term Identification
AN8 M M Copied from the 010x message.
042 Card Acceptor Identification Code
ANS15 O C May be returned, if received in the request, if the Card-Issuer Processor desires to have this field returned in a reversal.
043 Card Acceptor Location AN40 O C
044 Additional Response Data
LLV AN25 C C
045 Track 1 LLV ANS76 C Required if received in 0100 message.
Table 3.12:
0110 Pre-authorization Response (cont.)
Requirements
047 Additional Data, National
LLLV ANS..100
C Electronic Commerce Indicators & UCAF data. 048 Merchant/Bank Name LLLV
ANS025
O C May be returned, if received in the request, if the Card-Issuer Processor desires to have this field returned in a reversal.
049 Currency Code, Transaction
N3 M M Copied from the 010x message. 050 Currency Code, Settlement N3 C C Multi-Currency Field 051 Currency Code, Cardholder Billing N3 C C Multi-Currency Field 054 Additional Amounts LLLV ANS120 C C Return if additional amounts are needed or balance returned. 055 Additional Fees LLLV
ANS088
C C Required if received in the 0xxx message 057 Authorization Life LLLV N003 O O Reversal
058 National
Point-Of-Service Condition Code
LLLV N010 M M May be returned, if received in the request, if the Card-Issuer Processor desires to have this field returned in a reversal. 059 National Point-Of-Service Geographic Data LLLV AN017
O C Not used by the STAR network, but may be required by interfacing networks.
061 Acquirer Transport Data LLLV ANS100 O C Required if in 010x message. 063 STAR Data LLLV ANS050 M M
Table 3.12:
0110 Pre-authorization Response (cont.)
Requirements