POSLine ISO8583 Interface Specifications
POSLine ISO8583 Specifications
Revision History
Author
Revision Date
Comments
Christodoulos
Stavrou
Vangelis
Anastasiades
Akis Sykopetritis
01/06/01
Initial Creation of Document
06/07/01
Chip Support Added
07/07/01
Akis Sykopetritis
14/11/01
PID01191,
RN12565
PID01191,
RN12565
Christodoulos
Stavrou
Andrey
Brook
17/01/2003
Christodoulos
Stavrou
Christodoulos
Stavrou
Christodoulos
Stavrou
Christodoulos
Stavrou
Christodoulos
Stavrou
02-04-03
Update field 63 to support
Installments
Update field 63 for
instalment response
processing
Added the OTB-Settlement
Table
Added P2P support
(processing code 10 and
filed 48)
Updated Chip related fields
17-02-04
Added LRC on TCP/IP
MSCC
ONLINE 3.4r10+
03-05-04
Added Payment Indicator
EB
ONLINE 3.4r10+
26-11-04
MSCC
Christodoulos
Stavrou
Christodoulos
Stavrou
Christodoulos
17-02-05
10-01-06
Added field 55 and made
field 62 mandatory
Added key fields section
and highlighted the timeout
cases of reconciliation
Updated key fields
explanation
Added value 79 for field 22
09-02-06
Added value 2 in Payment
29/01/2003
26-01-05
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
Reference
02 July 2013
Included in online
version
online 3.4r06+
online 3.4r07-1+
online 3.4r07-1+
online 3.4r07+
MSCC
MSCC
Compliance
06.1
WSCB
ONLINE 3,4R08+
Comment [C1]: TO BE
IMPLEMENTED
Page 1-48
POSLine ISO8583 Interface Specifications
Stavrou
Christodoulos
Stavrou
Christodoulos
Stavrou
Christodoulos
Stavrou
Christodoulos
Stavrou
Christodoulos
Stavrou
28-02-06
Maria Hadjiona
12/12/2011
Nikolas Parpas
Eirini Mari
31/08/2012
11/09/2012
12-10-2006
25-04-2007
25/04/2009
17/11/2009
Indicator (60) for Recurring
Payments
Added Table id 17 for 4DBC
Added support for PIN
Change
Added support for Fee
Amount in Field 63
Added Table 33 for KSN in
Field 063
Added Table 18 for
Terminal Serial Number in
Field 063
Reversed Offline Sale,
Acknowledgement
Multicurrency support
Purchase Fee Acquirer
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
CAMB
Comment [C2]: TO BE
IMPLEMENTED
HAIBP
CTL-R001
Available only for
3.7r02 and above
Comment [CS3]: To be implemented
Comment [CS4]: To be implemented
12-2 Release
RQM-2855
RQM - 2857
C12-12
C12-12
Page 2-48
POSLine ISO8583 Interface Specifications
Table of Contents
1.
Message Structure _____________________________________________________________ 7
1.1.
ASYNC Message Structure _________________________________________________________ 7
1.2.
SYNC (X25) Message Structure _____________________________________________________ 7
1.3.
TCP/IP Message Structure _________________________________________________________ 7
1.4.
Transport Protocol Data Unit (TPDU) ________________________________________________ 7
1.5.
Communication Set-up_____________________________________________________________ 8
1.6.
Application Data Structure _________________________________________________________ 8
1.6.1.
Message Type Identifier __________________________________________________________ 8
1.6.2.
Bit Map _______________________________________________________________________ 9
1.6.3.
DATA ELEMENTS ________________________________________________________________ 9
2.
Transaction Data ______________________________________________________________ 9
2.1.
Message Type / Processing Code Table _______________________________________________ 12
2.1.
Primary Account Number, Field 2 __________________________________________________ 12
2.2.
Processing Code, Field 3 __________________________________________________________ 13
2.2.1.
Account Selections______________________________________________________________________ 13
2.3.
Processing / Flow Control Definition _________________________________________________________ 13
2.4.
Amount, Transaction, Field 4 ______________________________________________________ 13
2.5.
Systems Trace Audit Number, Field 11 ______________________________________________ 13
2.6.
Time, Local Transaction, Field 12 ___________________________________________________ 13
2.7.
Date, Local Transaction, Field 13 ___________________________________________________ 13
2.8.
Date, Expiration, Field 14 _________________________________________________________ 13
2.9.
Point of Service (POS) Entry Mode, Field 22 __________________________________________ 13
2.10.
Network International Identifier (NII), Field 24______________________________________ 14
2.11.
Point of Service (POS) Condition Code, Field 25 _____________________________________ 14
2.12.
Fee Amount, Field 28 ___________________________________________________________ 14
2.13.
Track II Data, Field 35 __________________________________________________________ 14
2.14.
Retrieval Reference Number (RRN), Field 37 _______________________________________ 14
2.15.
Authorization Identification Response, Field 38 ______________________________________ 14
2.16.
Response Code, Field 39 _________________________________________________________ 14
2.17.
Card Acceptor Terminal Id., Field 41 ______________________________________________ 14
2.18.
Card Acceptor Acquirer Id., Field 42 ______________________________________________ 15
2.19.
Card Acceptor Acquirer Name, Field 43 ____________________________________________ 15
2.20.
Track I Data, Field 45 ___________________________________________________________ 15
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 3-48
POSLine ISO8583 Interface Specifications
2.21.
Additional Text Data, Field 48 ____________________________________________________ 15
2.22.
Currency Code, Field 49 _________________________________________________________ 16
2.23.
Personal Identification Number (PIN) Data, Field 52 _________________________________ 16
2.24.
Security Related Control Information, Field 53 ______________________________________ 16
2.25.
Additional Amounts, Field 54 ____________________________________________________ 16
2.26.
ICC Related Data, Field 55 ______________________________________________________ 16
2.27.
Private Use Fields ______________________________________________________________ 17
2.27.1.
Private Use Field 60 ___________________________________________________________ 17
2.27.1.1.
Batch Number _______________________________________________________________ 17
2.27.1.2.
Original Message Data ________________________________________________________ 17
2.27.1.3.
Original Amount _____________________________________________________________ 17
2.27.2.
Private Use Field 62 ___________________________________________________________ 18
2.27.2.1.
Invoice/ECR Reference Number ________________________________________________ 18
2.27.3.
Private Use Field 63 ___________________________________________________________ 18
2.27.3.1.
Section 1 - Reconciliation Request Totals _________________________________________ 18
2.27.3.2.
Section 2 - Reconciliation Request Totals (Multi-Currency processing, Option 2) _________ 19
2.27.3.3.
Section 3 – Balance Inquiry Response ____________________________________________ 20
2.27.3.4.
Section 4 - Additional Data _____________________________________________________ 20
2.27.3.4.1.
P2P Data (10) _____________________________________________________________ 21
2.27.3.4.2.
P2P/Payment Data (11)______________________________________________________ 21
2.27.3.4.3.
CVV2 DATA (16)___________________________________________________________ 22
2.27.3.4.4.
AMEX 4DBC (17) __________________________________________________________ 23
2.27.3.4.5.
Installment Data (90) ________________________________________________________ 23
2.27.3.4.6.
Payment Indicator (60) ______________________________________________________ 24
2.27.3.4.7.
New PIN (77) ______________________________________________________________ 24
2.27.3.4.8.
Additional Fee Data (44) _____________________________________________________ 24
2.27.3.4.9.
KSN (33) _________________________________________________________________ 25
2.27.3.4.10.
2.28.
3.
Terminal Serial Number (18) _______________________________________________ 25
Key Fields ____________________________________________________________________ 25
Transaction Format Definitions _________________________________________________ 26
3.1.
Authorization/ Preauthorization ____________________________________________________ 26
3.2.
Balance Inquiry/Fee Inquiry _______________________________________________________ 26
3.3.
Sale / Debit _____________________________________________________________________ 27
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 4-48
POSLine ISO8583 Interface Specifications
3.4.
Refund _________________________________________________________________________ 28
3.5.
Cash ___________________________________________________________________________ 29
3.6.
Sale & Cash_____________________________________________________________________ 29
3.7.
Off-line Sale ____________________________________________________________________ 30
3.8.
Off-line Refund __________________________________________________________________ 31
3.9.
Adjust, Sale _____________________________________________________________________ 31
3.10.
Adjust, Credit _________________________________________________________________ 32
3.11.
Void, Sale _____________________________________________________________________ 33
3.12.
Void, Credit ___________________________________________________________________ 34
3.13.
Reversal ______________________________________________________________________ 34
3.14.
Test Transaction _______________________________________________________________ 35
3.15.
Please Wait Advice _____________________________________________________________ 37
3.16.
Settlement ____________________________________________________________________ 37
3.17.
Settlement Trailer ______________________________________________________________ 38
3.18.
Batch Upload __________________________________________________________________ 39
4.
Message Flows ______________________________________________________________ 40
4.1.
MESSAGE TYPE: 0100 _____________________________________________________________ 40
4.2.
MESSAGE TYPE: 0200 _____________________________________________________________ 40
4.3.
MESSAGE TYPE: 0200 - REFUND_____________________________________________________ 40
BASE I ______________________________________________________________________________ 40
POSLINE ____________________________________________________________________________ 40
4.4.
MESSAGE TYPE: 0200 - VOID REFUND ________________________________________________ 41
4.5.
MESSAGE TYPE: 0200 - VOID SALE __________________________________________________ 41
4.6.
MESSAGE TYPE: 0220 _____________________________________________________________ 41
4.7.
MESSAGE TYPE: 0400 - REVERSAL __________________________________________________ 42
4.8.
MESSAGE TYPE: 0500 - SETTLEMENT ________________________________________________ 42
4.9.
MESSAGE TYPE: 0320 - BATCH UPLOAD ______________________________________________ 42
4.10.
MESSAGE TYPE: 0800 ___________________________________________________________ 42
4.11.
MESSAGE TYPE: 0830 ___________________________________________________________ 43
5.
Settlement Process Flow _______________________________________________________ 43
5.1.
Balanced Settlement ______________________________________________________________ 43
5.2.
Balanced Settlement With Advices __________________________________________________ 43
5.3.
Out Of Balance Settlement ________________________________________________________ 44
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 5-48
POSLine ISO8583 Interface Specifications
5.4.
Balanced Settlement Or Batch Upload Time Out ______________________________________ 45
5.5.
Delayed Settlement _______________________________________________________________ 45
6.
Multicurrency Processing ______________________________________________________ 45
6.1.
Option 1. Standard. ______________________________________________________________ 45
6.2.
Option 2. Multi-currency merchant _________________________________________________ 45
7.
Payment System Support _______________________________________________________ 46
8.
Installment Processing ________________________________________________________ 46
9. OTB-Settlement Table ___________________________________________________________ 47
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 6-48
POSLine ISO8583 Interface Specifications
1. Message Structure
The structure of a terminal/host message consists of two major parts, the TPDU and Application Data. Depending on the
Communication Protocol (Controller Card in NAC), the message may have leading and/or trailing protocol-related
information.
1.1.
ASYNC Message Structure
Start
Chr
STX
Message
Length
Ascii 2
TPDU + Data
60h or 68h
1 Byte
4 Bytes BCD
1 Byte
1.2.
TPDU
Id
Dest.
Addr.
No
check
Orig.
Addr.
No check
2 Byt.
2 Byt.
App. Data
End
Chr
ETX
LRC
ISO8583
Message
Ascii
3
10 – 240
Bytes
1
Byte
XOr Operation with the
Message Length, TPDU,
Data and ETX.
1 Byte
SYNC (X25) Message Structure
Id
60h or 68h
TPDU
Dest. Addr.
No check
Orig. Addr.
No check
ISO8583 Message
1 Byte
2 Byt.
2 Byt.
10 – 240 Bytes
1.3.
TCP/IP Message Structure
Message
Length
Number
of bytes
following
in Hex
2 Bytes
Application Data
TPDU
Id
Dest. Addr.
60h or
68h
or
61h
or 62h
1 Byte
Application Data
No check
Orig.
Addr.
No check
ISO8583 Message
2 Bytes
2 Bytes
10 – 240 Bytes
LRC
(Conditional, exists if id in TPDU
is 61h)
XOr Operation with the TPDU
and Application Data.
The Message Length is not taken
in consideration.
1 Byte
Note:
LRC Failure
In case that the LRC verification fails, a message having only TPDU will be returned as response. In this
case, id in TPDU will have the value 62h.
1.4.
Transport Protocol Data Unit (TPDU)
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 7-48
POSLine ISO8583 Interface Specifications
The TPDU contains addressing information currently not used by the Host.
Host will only accept the as Id the values 60h or 68h. Any other value will be ignored.
The Destination Address is switched with the Originator Address in the Response TPDU.
1.5.
Communication Set-up
Single Session is expected which remains active through out. All messages will be exchanged through this
session.
That is, for X25 protocol only one SVS is required which remains active, for TCP/IP only one Socket is
required which remains open.
1.6.
Application Data Structure
Each application message consists of three components in the following sequence; Message Type Identifier, Bit Map, and a
variable number of data elements. The maximum data content of a message is 240 bytes.
Msg.Type
2 bytes
Bit Map
8 bytes
Application data
Data Elements
0-230 bytes
10-240
1.6.1.
Message Type Identifier
The Message Type Identifier (Msg.Type) consists of four (4) digits and is used to define the message type
of the transaction.
The first and second digits identify the class of message. The third and fourth digits identify the message
function and transmission mode:
Message type definition:
Digits 1 and 2
01
02
03
04
05
08
Message Class
Authorization
Financial
Batch Upload
Reversal
Reconciliation control
Network management
Digits 3 and 4
00
10
20
30
Transmission Mode
Interactive request
Interactive response
Non-interactive advice
Non-interactive advice response
The following Message Type Identifiers are used:
Message Type
0100/0110
0200/0210
0220/0230
0320/0330
0400/0410
Application
Authorization Request/Response
Financial Transaction Request/Response
Financial Transaction Advice/Response
Batch Upload/Response
Reversal Request/Response
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 8-48
POSLine ISO8583 Interface Specifications
0500/0510
0800/0810
1.6.2.
Reconciliation Request/Response
Network Management Request/Response
Bit Map
ISO 8583 uses a concept called "bit map", where each data element is assigned a position indicator in a control field, or bit map.
The presence of a data element in a specific message is indicated by a one (1) in the assigned position; the absence of a data
element is indicated by a zero (0) in the assigned position.
Each application transaction includes one (1) bit map. A bit map consists of 64 bits numbered from the left
starting with bit 1.
The first bit of the bit map represents a secondary bit map. Since no secondary bit map is supported, the first
bit of the bit map is always „0‟.
bit
1
Field 1
Secondary bit
map
Always „0‟
2
Field 2
Primary Acct No.
3
Field 3
Processing Code
4
Field 4
Amount, Trans
•••••
64
Field 64
Message Auth
Code
1.6.3.
DATA ELEMENTS
Data Element characteristics - names, formats, attributes, conditional code values - are described fully
in the current specification.
The following rules apply to the data elements within a message:
All data elements begin on a byte boundary.
Fixed length “n” type fields with an odd length are right-justified to a byte boundary, and zero-filled on
the left. For example, a field type “n3” field will occupy 2 bytes, and the most significant nibble of the
first byte will be 0.
All lengths for variable length fields are represented in binary coded decimal (BCD), right-justified to a
byte boundary, and zero-filled on the left. For example, an „LLVAR‟ field with a length of 15 will have
a length indicator of „15h‟ occupying one byte. An „LLLVAR‟ field with a length of 15 will have a
length indicator of „0015h‟, occupying two bytes.
The length indicator for a variable length field is a count of the number of data elements to follow. It
does not include the length of the length indicator.
The variable length Primary Account Number field, field 2, with an odd length is left justified within
the field and “F” filled.
If the message contains a field not descripted in this specification then the message will not be
processed therefore no response will be send from the Host.
2. Transaction Data
The following table shows the fields as implemented by the Host. This section will describe the use of the following table and
define each field.
Bit Data Element Name
Message Type Id
Attribute
n
4
Request
Response Comments
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 9-48
POSLine ISO8583 Interface Specifications
02
03
04
11
12
13
14
22
24
25
28
35
37
38
39
41
42
43
45
48
49
52
53
54
55
60
61
62
63
64
Bit Map
Primary Acct. Num.
Processing Code
Amount, Trans.
Systems Trace No
Time, Local Trans.
Date, Local Trans.
Date, Expiration
POS Entry Mode
NII
POS Condition Code
Fee Amount
Track 2 Data
Retrieval Ref. No.
Auth. Id. Response
Response Code
Terminal Id
Card Acq. Id
Card Acq. Name
Track 1 Data
Additional Text Data
Currency Code
PIN Data
Security Control Info
Additional Amounts
ICC Related Data
Private Use
Private Use
Private Use
Private Use
Message Auth. Code
b
64
n
..19
n
6
n
12
n
6
n
6
n
4
n
4
n
3
n
3
n
2
n
12
z
..37
an
12
an
6
an
2
ans
8
ans
15
ans
40
ans ..76
ans ..999
n
3
B
64
N
16
an ...120
b …255
ans ...999
ans ...999
ans ...999
ans ...999
b
64
Mandatory for multi-currency processing. Option 2
NOT USED
The first two columns, Bit, Data Element Name show the data element assignment to a bit position, refer to Table 2 ISO
8583. The following sections will define the use of each field.
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 10-48
POSLine ISO8583 Interface Specifications
The “Attribute” column lists the format and size of the data element. The size of the field is the number of data elements
contained in the field. Variable length fields are shown with preceding “.” characters indicating the number of variable leng th
digits. (...999 defines a field that‟s maximum length is 999 data elements.) The following table defines each attribute.
Attribute Meaning
A
Alpha characters (a-z, A-Z)
Each data element represents 1 byte
An
Alpha-numeric characters (1-9, a-z, A-Z)
Each data element represents 1 byte
Ans
Alpha-numeric and special characters (All characters)
Each data element represents 1 byte
B
Binary data
Each data element represents 1 bit. (8 data elements = 1 byte)
N
Numeric data
Each data element represents 1 nibble (2 data elements = 1 byte)
Z
Track 2 data, as read from the magnetic strip.
Each data element represents 1 nibble (2 data elements = 1 byte)
K
Key Field, Refer to section 2.6 Key fields for more information
The “Request” and “Response” columns show the contents of the terminal request and response messages comprising a
transaction. These contents can be one of the following:
M
O
Cxx
01
02
03
04
05
06
07
Mandatory
Optional
Conditional field, where xx is:
The primary account number is included when the transaction is entered manually via the keyboard.
The expiration date field will be included if the card number was entered manually, and the card processing
options are set to accept a date, expiration to be entered.
For on-line transactions when the account number is read from the magnetic stripe reader track I and/or
track II will be included.
Terminal only stores the primary account number and expiration date from a track read. Any transactions
processed other than an on-line transaction will include the primary account number and expiration date.
The first two digits of the POS entry mode will be set to „02‟ if the card is read by the card reader, and „01‟
if the card number is entered via the keyboard. The last digit will indicate the PIN entry capability of the
terminal. It will have a value of „1‟ if there is PIN entry capability, and „2‟ if there is no PIN entry
capability. This information should be treated as additional transaction information, and not used to
determine which field to use for the card number.
Some check guarantee services use primary account numbers for data. If account number is entered
manually the bit 2 will be included in the request. If the account number is read via the magnetic card
reader then either track I and/or track II will be included.
Present if Chip Card was used.
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 11-48
POSLine ISO8583 Interface Specifications
2.1.
Message Type / Processing Code Table
The following is a table specifying the message type and processing code for each transaction type. The
stroked through messages are mentioned in the Specifications but are not supported by the Host.
Transaction
Message Type
Authorization
0100
Pre-Authorization
Balance Inquiry
Fee Inquiry
Check Verification
Card Verification
PIN Change
Sale
0200
P2P
Refund
Payment
Cash
Sale & Cash
Void, Sale, on-line
Void, Refund, on-line
Off-line Sale
0220
Off-line Refund
Sales Completion
Adjust, Sale
Adjust, Refund
Guaranteed Late Arrival
Reversal
0400
Settlement Request
0500
Settlement, after upload
Batch Down Line Load
Batch upload
0320
Signature Data
0320
Statistics
0800
Logon
Initialization
Test Transaction
0800
Please Wait Advice
0830
EBT Food Stamps
0200
EBT Cash Card Purchase
EBT Cash w/Cash Back
EBT Cash Only
a = Account Selection
x = Processing / Flow control
Processing Code
00 a0 0x
30 a0 0x
31 a0 0x
32a0 0x
04 a0 0x
38 a0 0x
70 a0 0x
00 a0 0x
10 a0 0x
20 a0 0x
50 a0 0x
01 a0 0x
09 a0 0x
02 a0 0x
22 a0 0x
00 a0 0x
20 a0 0x
00 a0 0x
02 a0 0x
22 a0 0x
90 a0 0x
Same as original transaction
92 00 0x
96 00 0x
95 00 0x
Same as original transaction
90 00 0x
91 00 0x
92 00 0x
93 00 0x
99 00 0x
90 00 0x
00 a8 0x
00 a0 0x
09 a0 0x
01 a0 0x
2.1. Primary Account Number, Field 2
The Primary Account Number (PAN) contains the card account number when track I or track II is not
available. The PAN is sent on all advice transactions (i.e. adjust, off-line, etc.).
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 12-48
POSLine ISO8583 Interface Specifications
2.2. Processing Code, Field 3
The processing code is used in conjunction with the message type to define the type of transaction being
sent by the terminal to the host. It also includes account selection information.
For example:
00 a0 0x
where
a = Account Selection
x = Processing / Flow control
2.2.1. Account Selections
The account information is represented in the third digit of the processing code. The following values are
used:
Code
0
1
2
3
4
9
Account Selected
Default Account
Savings Account
Checking Account
Credit Facility
Universal Account
EBT
2.3. Processing / Flow Control Definition
Host does not use this information. It is returned in the Response.
2.4. Amount, Transaction, Field 4
The transaction amount is the total amount of the transaction.
2.5. Systems Trace Audit Number, Field 11
The systems trace audit number (STAN) is generated automatically by the terminal. It is incremented for
each transaction processed. The terminal will never generate a STAN of 000000.
2.6. Time, Local Transaction, Field 12
The time stamp of the transaction when it originally was entered. This time stamp is permanent, it does not
change on subsequent transactions (i.e. adjust).
2.7. Date, Local Transaction, Field 13
The date stamp of the transaction when it originally was entered. This date stamp is permanent, it does not
change on subsequent transactions (i.e. adjust).
2.8. Date, Expiration, Field 14
The expiration date of the PAN. It is included when the track I or track II data is not present. The
expiration date is included as part of the track data when track data is present.
2.9. Point of Service (POS) Entry Mode, Field 22
The POS entry mode is used to indicate how the primary account number was entered into the terminal.
Positions 1 and 2
00
01
02
05
79
PAN entry mode
Unspecified
Manual
Magnetic stripe
ICC Read
Manual PAN entry as a
fallback to PAN entry via ICC
Position 3
0
1
2
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
PIN entry capability
Unspecified
PIN entry capability
No PIN entry capability
02 July 2013
Page 13-48
POSLine ISO8583 Interface Specifications
80
95
when the chip card or chipcapable terminal is unable to
process the transaction using
the data on the chip or
magnetic stripe.
Mag Stripe even though it is an
ICC capable
Integrated circuit card; CVV data
may be unreliable
2.10. Network International Identifier (NII), Field 24
The NII is used to identify the acquiring host.
2.11. Point of Service (POS) Condition Code, Field 25
The POS condition code is used to identify the condition which the transaction takes place.
Code
00
04
05
06
08
51
52
Meaning
Normal presentment
ECR Interface
Card not present
Pre-authorized request
Mail and/or telephone order
Open Tab
Frequency transaction
2.12. Fee Amount, Field 28
The Fee Amount is present when in a Fee Inquiry response and in every financial transaction response for
which the acquirer has added a Fee. The Fee amount is in the Transaction Currency (Field 49) with implied
decimal places.
2.13. Track II Data, Field 35
The Track II data field is present when valid track II is used to initiate the transaction. It contains the track II
image excluding the start sentinel, end sentinel and LRC characters.
2.14. Retrieval Reference Number (RRN), Field 37
The RRN is assigned by the host. The terminal stores the reference number and includes it on all advice
transactions. If an advice receives a new RRN the terminal will replace the old RRN with the new value.
2.15. Authorization Identification Response, Field 38
Usually referred to as the “approval code.” Assigned by the authorization host when the transaction is
approved.
2.16. Response Code, Field 39
Returned to the terminal from the authorization host to indicate the status of the transaction. A “00”
response code indicates an approval status. All other values are non-approval or error responses
2.17. Card Acceptor Terminal Id., Field 41
The terminal id used to uniquely identify the terminal. In case of Multicurrency support (Option 1), the
Terminal ID is different for each currency. In case of Multi-currency support (Option 2), the same Terminal
ID can be use for up to 4 currencies.
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 14-48
POSLine ISO8583 Interface Specifications
2.18. Card Acceptor Acquirer Id., Field 42
The merchant number assigned to the terminal. In case of Multicurrency support (Option 1), the Merchant
ID is different for each currency. In case of Multi-currency support (Option 2), the same Merchant ID can
be use for up to 4 currencies.
2.19. Card Acceptor Acquirer Name, Field 43
The name of the establishment. This field is typically not used. The name and address for the printer is
loaded in the terminal configuration table.
2.20. Track I Data, Field 45
The Track I data field is present when valid track II is used to initiate the transaction. It contains the track I
image excluding the start sentinel, end sentinel and LRC characters.
2.21. Additional Text Data, Field 48
The additional text data field can be used:
1. For capturing text data send by the POS terminal.
The contents may vary based on the implementation:
1.1. Account Funding Transaction Details:
The field should start with „USRDT „ followed by any text data up to 100 characters.
2. Requesting the Fee for a transaction (Fee Inquiry). In this case, the field should have the next format:
FEEINQnn where
- „FEEINQ‟ is a hardcoded string
- nn is a two digit code which identifies the transaction code for which the fee inquiry is requested.
The table below shows the possible values of nn
Code
00
01
10
11
20
30
38
40
50
90
91
92
93
97
Transaction Description
Purchase
Cash
P2P
Quasi Cash
Credit
Balance Inquiry
Mini Statement
Funds Transfer
Payment
PIN change
Deposit
Checkbook request
Full Statement
PIN Unblock
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 15-48
POSLine ISO8583 Interface Specifications
2.22. Currency Code, Field 49
Field 49 contains a code that identifies the currency of Field 4 (Transaction amount). This field is
mandatory for multi-currency processing (Option 2).
2.23. Personal Identification Number (PIN) Data, Field 52
PIN data as received from the PIN pad.
2.24. Security Related Control Information, Field 53
The security related control information is used to identify the terminal to the host. Its use is application
dependant.
2.25. Additional Amounts, Field 54
The additional amounts field contains other amounts associated with the transaction for example tip or cash
back or balance inquiry
Field
Length Attribute
Additional Amount
Attribute Bytes Values
n
3
2 0LLL - BCD length of data to follow, maximum 120 digits.
an 12..13 12..13 For Tip Amount only 12 bytes are required (only the amount).
For Cashback Amount only 12 bytes are required (only the amount).
For Balance Inquiry 13 bytes, are required with the next contents:
1. First 12 bytes are the Balance Inquiry Amount
2. The 13 byte is „C‟ for Positive Balance Inquiry Amount or „D‟
for Negative Balance Inquiry Amount.
2.26. ICC Related Data, Field 55
This field is used to transport chip-specific data over . For EMV compliant ICC data, DE 055 has its own generic structure
and may contain one or more Private Data Sub-elemnts (PDS‟s) as shown in the figure below:
Variable data zone – max 255 bytes
One or more PDS occurrences
Length
First PDS
PDS Tag
Second PDS
Length
Nth pds
PDS Data
More information can be found in the Europay,MasterCard,and Visa (MV ‟96) chip specification. EMV uses Basic encoding
Rules (B R). Reference the EMV ‟96 specification for details regarding coding of BER-tag,length,value (TLV) data objects.
There are mandatory tags that need to be send for both online and offline transactions.
Refer to EMV Tags for Field 55 document for more information.
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 16-48
POSLine ISO8583 Interface Specifications
2.27. Private Use Fields
Use has been made of private fields to provide for Data Elements not included in ISO 8583 and these are
defined in the following section, and referenced in the message format section.
Field
60
61
62
63
Name
Batch Number
Software ID
Original Message Data
Terminal Configuration Parameters (T4/T6)
Original Amount
Logon Request
Product Codes
Card Definition Tables (T4/T6)
Invoice/ECR Reference Number
Reconciliation Response Text
Product codes (T4/T6 Table Load to Terminal)
Logon Response
Reconciliation Request Totals
Terminal Statistics
Lodging Details
Additional Data
Applicable Message Type
0500
0800
0320
0810
0220
0800
0100, 0200, 0220, 0320
0810
0100, 0200, 0220, 0320
0510
0810
0810
0500
0800
0220
0100, 0200, 0220, 0320, 0110, 0210, 0310, 0510, 0810
2.27.1.
Private Use Field 60
The following sections define the use of each private use field 60.
2.27.1.1. Batch Number
The batch number is sent to the host in the settlement request message (message type 0500). The batch
number is assigned by the terminal when the batch is closed. Batch numbers may be set during terminal
initialization.
Message Type: 0500
Field
Length Attribute
Batch Number
Attribute Bytes Values
n
3
2 0LLL - BCD length of data to follow
ans
6
6
2.27.1.2. Original Message Data
The original message data is used to carry data in the transaction upload (message type 0320) of the original
transaction, since the message type and system trace audit number of the 0320 is not the same as the
original transaction.
Message Type: 0320
Field
Length Attribute
Original Message Type
Original Systems Trace
Audit Number
Reserved
Attribute
n
3
an
4
an
6
an
12
Bytes
2
4
6
Values
0LLL - BCD length of data to follow
Message type of original transaction
Trace number of original transaction
12 Space fill - Reserved for future use.
2.27.1.3. Original Amount
The original amount field is used to carry the amount of the transaction prior to a void or adjustment.
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 17-48
POSLine ISO8583 Interface Specifications
Message Type: 0220
Field
Length Attribute
Original Amount
Attribute Bytes Values
n
3
2 0LLL - BCD Length of data to follow
an
12
12 Original amount of the transaction being adjusted
2.27.2.
Private Use Field 62
The following sections define the use of each private use field 62.
2.27.2.1. Invoice/ECR Reference Number
Message Type: 0100, 0200, 0220, 0320, 0400
Field
Length Attribute
Invoice/ECR reference
number
2.27.3.
Attribute Bytes Values
n
3
2 0LLL – BCD Length of data to follow
an
6
6 Invoice number as entered by the operator or generated
automatically by the terminal. Must be unique within the same
Batch. This is the key field to be used for the above messages.
Private Use Field 63
The following sections define the use of each private use field 63. Only one section is applicable at a time. A
request/response can not contain more than one section.
2.27.3.1. Section 1 - Reconciliation Request Totals
The reconciliation totals are sent to the host in the settlement message (message type 0500). The totals are
all the financial transactions of the current open batch. In the case of multi-host applications, the totals are
only those totals associated with each acquirer.
Message Type: 0500
Field
Length Attribute
First Set
Sales Count
Sales Amount
Refund Count
Refund Amount
Second Set
Sales Count
Sales Amount
Refund Count
Refund Amount
Third Set
Sales Count
Sales Amount
Refund Count
Refund Amount
Forth Set
Sales Count
Sales Amount
Refund Count
Refund Amount
Attribute Bytes Values
N
3
2 0LLL - BCD Length of data to follow
an
3
3 000-999
an
12
12 $$$$$$$$$$¢¢
an
3
3 000-999
an
12
12 $$$$$$$$$$¢¢
an
3
3 000-999
an
12
12 $$$$$$$$$$¢¢
an
3
3 000-999
an
12
12 $$$$$$$$$$¢¢
an
3
3 000
an
12
12 000000000000
an
3
3 000
an
12
12 000000000000
an
3
3 000-999
an
12
12 $$$$$$$$$$¢¢
an
3
3 000-999
an
12
12 $$$$$$$$$$¢¢
The Reconciliation Totals are calculated using the following rules:
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 18-48
POSLine ISO8583 Interface Specifications
Any set of fields (First, Second, Third) can be used to contain the totals. The Host will sum up these
totals to a Total Sales Count, Total Sales Amount, Total Refund Count and Total Refund Amount.
The Fourth Set of totals is ignored.
The totals do not include any Reversals since a reversal and its original will be cancelled out.
Refund Totals (amount/count) refer only to the Refund requests (and the Adjustment Refund if any)
Sales Totals (amount/count) refer to the transactions other than Refund (or the Adjustment Refund)
and do not include the authorizations.
2.27.3.2. Section 2 - Reconciliation Request Totals (Multi-Currency processing, Option 2)
The reconciliation totals are sent to the host in the settlement message (message type 0500).
The totals are all the financial transactions of the current open batch.
In the case of multi-currency terminals the totals are associated with specific currencies.
Number of currencies and sets is limited to 4.
For backward compatibility format of first 120 bytes are the same as described in Section 1. Each set
contains totals for currency specified in positions 121-132. Currency is specified if totals in corresponding
set are presented. For example, for two currencies length of field 63 is 126=30*4+3*2.
Message Type: 0500
Field
Length Attribute
Attribute Bytes Values
N
3
2 0LLL - BCD
Length of data to
follow
First Set
Comments
Mandatory
Sales Count
Sales Amount
Refund Count
Refund Amount
Second Set
Sales Count
Sales Amount
Refund Count
Refund Amount
Third Set
Sales Count
Sales Amount
Refund Count
Refund Amount
an
an
an
an
3
12
3
12
3
12
3
12
000-999
$$$$$$$$$$¢¢
000-999
$$$$$$$$$$¢¢
an
an
an
an
3
12
3
12
3
12
3
12
000-999
$$$$$$$$$$¢¢
000-999
$$$$$$$$$$¢¢
an
an
an
an
3
12
3
12
3
12
3
12
000-999
$$$$$$$$$$¢¢
000-999
$$$$$$$$$$¢¢
an
an
an
an
3
12
3
12
3
12
3
12
000-999
$$$$$$$$$$¢¢
000-999
$$$$$$$$$$¢¢
n
n
n
n
3
3
3
3
3
3
3
3
Fourth Set
Sales Count
Sales Amount
Refund Count
Refund Amount
First CurrencyCode
Second Currency Code
Third Currency Code
Fourth Currency Code
ISO code
ISO code
ISO code
ISO code
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
Optional
If not presented should be filled by 30 spaces
(0x20)
Optional
If not presented should be filled by 30 spaces
(0x20)
Optional
If not presented should be filled by 30 spaces
(0x20)
Mandatory
Conditional. If totals in 2nd set presented
Conditional. If totals in 3rd set presented
Conditional. If totals in 4th set presented
02 July 2013
Page 19-48
POSLine ISO8583 Interface Specifications
The Reconciliation Totals are calculated using the following rules:
Any set of fields is used to contain the totals for specific currency. The Host will sum up these totals to
a Total Sales Count, Total Sales Amount, Total Refund Count and Total Refund Amount.
The totals do not include any Reversals since a reversal and its original will be cancelled out.
Refund Totals (amount/count) refer only to the Refund requests (and the Adjustment Refund if any)
Sales Totals (amount/count) refer to the transactions other than Refund (or the Adjustment Refund).
2.27.3.3. Section 3 – Balance Inquiry Response
Message Type: 0110, 0210
Field
Length Attribute
Balance Currency
Attribute Bytes Values
N
3
2 0LLL - BCD Length of data to follow
an
3
3 ISO Alpha Code
an
1
1 [space]
an
1
1 Balance Sign:
[-] for Negative Balance
[space] for Positive Balance
an
12
12 The Balance Amount in Balance Currency (no decimals implied)
Balance Sign
Balance Amount
2.27.3.4. Section 4 - Additional Data
Message Type: 0100, 0200, 0220, 0320, 0110, 0210, 0310, 0510 and 0810
The additional data can consist of one or more of the following fields immediately following each other.
Each of the fields contains its own length indicator to allow any fields that are not recognized by the host to
be stepped over and ignored, with any following fields still being processed successfully.
Field
Length Attribute
Additional Data (1)
Additional Data (2)
.
.
.
.
.
.
Additional Data (x)
Attribute
n3
.
.
.
.
.
.
Bytes
2
var
var
.
.
.
.
.
.
var
Values
„0LLL‟ – BCD length of the data to follow
First additional data element
Second additional data elements
The additional data can be any number of data elements in any
order. Each data element contains its own identifier and length.
Unknown elements may be skipped over.
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 20-48
POSLine ISO8583 Interface Specifications
2.27.3.4.1.
P2P Data (10)
Message type '0200', processing code '10' (Deprecated refer to P2P Data (11), Only for ON-US)
Field 063 is used to carry the sender‟s and recipient‟s information, such as the card number to be credited
(recipient). For this purpose, a new usage is defined for this field, called “P2P Data” with table ID “10”:
Field
Additional Data Length
Table Id
Request Processing
Recipient Account Number
Sender Reference Number
Sender Name
Attribute
n4
ans 2
Bytes
2
2
Values
„0LLL‟ – BCD length of the data to follow.
„10‟ – P2P Data.
n 19
ans 16
ans 51
19
16
51
Sender Address
ans 40
40
Sender City
ans 25
25
Sender State/Province
a2
2
Sender Country
a3
3
The card number to be credited. Mandatory.
The sender‟s reference number.
This tag contains the sender‟s name in the following
format:
- First Name
- Space (as a delimiter)
- Last Name
e.g. “John Doe”
Optional*.
The sender‟s address.
Optional*.
The sender‟s city.
Optional*.
The sender‟s State/Province when sender‟s country is
USA or CAN.
Optional*.
The sender‟s 3-digit numeric country code.
Optional*.
* If any of the optional fields is used, all preceding optional unused fields must be filled with spaces. The length
indicator must be accounting for all data, up-to the last used field.
2.27.3.4.2.
P2P/Payment Data (11)
Message type '0200', processing code '10xxxx', „50xxxx‟
Field 063 is used to carry the sender‟s and recipient‟s information.The data of the field will be in TLV
format.
Field
Additional Data Length
Table Id
Request Processing
Tag
Length
Value
Attribute
n4
ans 2
Bytes
2
2
Values
„0LLL‟ – BCD length of the data to follow.
„11‟ – P2P/Payment Data.
an2
n2
ans
tag from the list below
„LL‟ – BCD length of the Value to follow
values, as described in the table below
Tag
an2
2
1
up to 99
…
2
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
tag from the list below
02 July 2013
Page 21-48
POSLine ISO8583 Interface Specifications
Length
Value
n2
ans
1
up to 99
„LL‟ – BCD length of the Value to follow
values, as described in the table below
The next tags are supported:
Tag
01
Format
ans 16
Field Name
Sender Reference Number
Description
Provided by the originator and uniquely
identifies the sender
(Required if Tag 02 not present.)
02
ans 34
Sender Account Number
03
04
05
06
07
21
22
23
24
ans 30
ans 50
ans 25
ans 3
ans 3
ans 10
ans 20
ans 45
Ans2
Sender Name
Sender Address
Sender City
Sender State
Sender Country
ZIP/Postal Code
Recipient Telephone Number
Text Message
Source of Funds
Contains the sender‟s card number or bank
account number from which the funds are to be
taken (debited).
(Required if Tag 01 not present)
Required for International
Required for International
Required for International
Required for International
Required for International
Required for International
Optional
Optional
Indicates the method used by the
sender to fund the payment:
Value
01
02
03
04
05
06
Description
Credit Card
Debit Card
Prepaid Card
Cash
Debit/Saving/Checking
Account
Credit Account other
than those linked to a
Credit Card.
Required for International (U.S. recipient
Issuers)
F2
Ans19
Receiver Card Number
Card that will receive the funds (to be credited)
Required for P2P
Note:
For Payment transaction, the receiver card is in
Field 2 and this tag is not used.
2.27.3.4.3.
CVV2 DATA (16)
Field
Additional Data Length
Attribute
n4
Bytes
2
Values
„0LLL‟ – BCD length of the data to follow
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 22-48
POSLine ISO8583 Interface Specifications
Table Id
Request Processing
Request Value
ans 2
2
„16‟ – CVV2 data
an 6
6
The 6 character CVV2 Request Value sent to the Host
Position 1
0 – CVV2 Value is intentionally not provided
1 – CVV2 Value is Present
2 – CVV2 Value is Present but illegible
9 – Cardholder states that no CVV2 value is imprinted
Position 2
0 – Only the normal Response Code should be returned
1 – Both the Response Code and the CVV2 Result Code should
be returned
Positions 3 - 6
The CVV2 Value as imprinted on the card
(right – justify and space fill the entry)
If position 1 = 0, 2, or 9, positions 3 – 6 should be space filled
Response Processing
Result Code
an 1
1
The 1 character CVV2 Result Code returned from the Host
M – CVV2 Match
N – CVV2 No Match
P – Not Processed
S – Merchant has indicated that CVV2 is not present on card
U – Issuer is not certified and / or has not provided Visa
encryption keys
2.27.3.4.4.
AMEX 4DBC (17)
Field
Additional Data Length
Table Id
Value
2.27.3.4.5.
Attribute
n4
ans 2
an 4
Bytes
2
2
4
Values
„0LLL‟ – BCD length of the data to follow
„17‟ – AMEX 4DBC
The 4DBC figure as it is printed on the AMEX Card
Installment Data (90)
Field
Additional Data Length
Table Id
Request Processing
Request Value
Attribute
n4
ans 2
an 4
Bytes
2
2
Values
„0LLL‟ – BCD length of the data to follow
„90‟ – Installment data
4
Positions 1 – 4
Loan Period in months with leading zeros
(For example: „0012‟ for 12 months)
Positions 5 – 8
Offset Period in months with leading zeros
(For example: „0012‟ for 12 months)
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
an4
4
Page 23-48
POSLine ISO8583 Interface Specifications
Response Processing
Result Code
an 40
40
Result returned from the Host for terminal prints
Positions 1 – 4
Loan Period
(For example: „0012‟ for 12 months)
Positions 4 – 16
Interest Rate
(For example: „00000002.000‟ for 2 %)
Positions 17 – 28
Amount of Monthly Amortization
Positions 29 – 40
Full Amount Including Interest
2.27.3.4.6.
Payment Indicator (60)
Field
Additional Data Length
Table Id
Request Processing
Request Value
2.27.3.4.7.
Field
an 1
Bytes
2
2
1
Values
„0LLL‟ – BCD length of the data to follow
„60‟ – Payment Indicator
„0‟ or not existing „1‟
„2‟
Refund Transaction
Payment transaction
Recurring Payment
Comment [C5]: TO BE IMPLEMETED
Comment [C6]: TO BE
IMPLEMENTED
New PIN (77)
Field
Additional Data Length
Table Id
Request Processing
Value
2.27.3.4.8.
Attribute
n4
ans 2
Attribute
n4
ans 2
an 16
Bytes
2
2
16
Values
„0LLL‟ – BCD length of the data to follow
„77‟ – New PIN Block encrypted under TPK (Same as Field 52)
New PIN Block in ASCII representation of HEX
Comment [C7]: TO BE
IMPLEMENTED
Additional Fee Data (44)
Attribute
Bytes
Values
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 24-48
POSLine ISO8583 Interface Specifications
Additional Data Length
Table Id
Response Processing
Value
n4
ans 2
2
2
„0LLL‟ – BCD length of the data to follow
„44‟ – Fee Amount that relates to this transaction
an 12
12
The Additional Fee is present in the responses (0210, 0110) for
ON-US authorizations only and if the Authorization Fee Module
has been licensed.
It contains the information about Fee associated with the
transaction from Issuer site, in the format:
cccSdddddddd
where
ccc is Fee currency (Numeric ISO)
S is the Sign flag and can have the values C (for
Credit Fee) or D (for Debit Fee)
dddddddd is the Fee amount with implied decimal
points in Fee currency.
2.27.3.4.9.
Comment [CS8]: To be implemented
KSN (33)
Field
Additional Data Length
Table Id
Request Processing
Request Value
Attribute
n4
ans 2
an 16
Bytes
2
2
Values
„0LLL‟ – BCD length of the data to follow
„33‟ – Key Serial Number(KSN)
16
The KSN up to 16 hexadecimal characters
Comment [CS9]: To be implemented
2.27.3.4.10. Terminal Serial Number (18)
Field
Additional Data Length
Table Id
Value
Attribute
n4
ans 2
an 25
Bytes
2
2
25
Values
„0LLL‟ – BCD length of the data to follow
„18‟ – Terminal Serial Number
The Terminal Serial Number up to 25 characters
2.28. Key Fields
The key fields are used to find any related transactions (0220, 0320, 400) to an original transaction (0100, 0200). These fields
needs to be echoed back to the response of any request and must have the same value of the original transaction (0100 or
0200)
Possible options are:
- Field 62 (Invoice/ECR Reference Number)
- Fields 12 Local Time, and 13 Local Date
OR
The table below shows the key fields used based on the existence of the fields 62, 12 and 13.
Fields 12 and 13 Present
Field 62 Present
Key field to be used: Field 62
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
Field 62 NOT present
Key field to be used: Fields 12 and 13
02 July 2013
Page 25-48
POSLine ISO8583 Interface Specifications
Field 12 and/or 13 NOT Present
Key field to be used: Field 62
INVALID CASE:
Field 62 must be present OR
Fields 12 and 13 must be present
3. Transaction Format Definitions
The following sections define the transactions that are used by the Host
3.1.
Authorization/ Preauthorization
Bit Data Element Name
Message Type Id
Bit Map
02 Primary Acct. Num.
03 Processing Code
04
11
12
13
14
22
24
25
28
35
37
38
39
41
42
43
45
48
49
52
53
54
55
60
61
62
63
64
3.2.
Attribute Request
N
4
0100
b
64
M
n
..19
C01
n
6 00a00x
or
30a00x
Amount, Trans.
n
12
M
Systems Trace No
n
6
M
Time, Local Trans.
n
6
K
Date, Local Trans.
n
4
K
Date, Expiration
n
4
C02
POS Entry Mode
n
3
C05
NII
n
3
M
POS Condition Code n
2
00
Fee Amount
n
12
Track 2 Data
z
..37
C03
Retrieval Ref. No.
an
12
Auth. Id. Response
an
6
Response Code
an
2
Terminal Id
ans
8
M
Card Acq. Id
ans
15
M
Card Acq. Name
ans
40
Track 1 Data
ans ..76
C03
Add. Data – Private
ans ...999
O
Currency Code
n
3
C
PIN Data
b
64
O
Security Control Info n
16
O
Additional Amounts an ...120
ICC Related data
b ...255
C07
Private Use
ans ...999
O
Product Codes
ans ...999
O
Invoice/ECR Ref #
ans ...999
K
Additional Data
ans ...999
O
Message Auth. Code b
64
O
Response Comments
0110
M
00a00x
or
30a00x
O
M
K
K
Authorization
Preauthorization
Amount is verified when included in response
M
O
M
O
M
M
O
O
In case of multi-currency processing (Option 2)
If PINs are selected
Use is application dependant
O
O
If Product codes are selected
K
O
O
If additional data is available
Balance Inquiry/Fee Inquiry
Bit Data Element Name Attribute Request Response Comments
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 26-48
POSLine ISO8583 Interface Specifications
Message Type Id
Bit Map
02 Primary Acct Num.
03 Processing Code
n
b
n
n
04
11
12
13
14
22
24
25
35
37
38
39
41
42
43
45
48
52
53
54
55
60
61
62
63
64
n
n
n
n
n
n
n
n
z
an
an
an
ans
ans
ans
ans
ans
b
n
an
b
ans
ans
ans
ans
b
3.3.
Amount, Trans.
Systems Trace No
Time, Local Trans.
Date, Local Trans.
Date, Expiration
POS Entry Mode
NII
POS Condition Code
Track 2 Data
Retrieval Ref No.
Auth. Id. Response
Response Code
Terminal Id
Card Acq. Id
Card Acq. Name
Track 1 Data
Add. Data - Private
PIN Data
Security Control Info
Additional Amounts
ICC Related data
Private Use
Private Use
Invoice/ECR Ref. #
Additional Data
Message Auth. Code
4
64
..19
6
12
6
6
4
4
3
3
2
..37
12
6
2
8
15
40
..76
...999
64
16
...120
...255
...999
...999
...999
...999
64
0100
M
C01
31a00x
or
32a00x
M
K
K
C02
C05
M
00
C03
M
M
C03
C
O
O
0110
M
31a00x
Or
32a00x
M
M
K
K
M
M
O
M
M
Required for Fee Inquiry
C07
O
O
O
K
O
O
K
O
O
Use is application dependant
Sale / Debit
Bit Data Element Name
Message Type Id
Bit Map
02 Primary Acct Num.
03 Processing Code
04 Amount, Trans.
11 Systems Trace No
12 Time, Local Trans.
13 Date, Local Trans.
14 Date, Expiration
22 POS Entry Mode
24 NII
25 POS Condition Code
28 Fee Amount
35 Track 2 Data
37 Retrieval Ref No.
Attribute Request
n
4
0200
b
64
M
n
..19
C01
n
6 00a00x
n
12
M
n
6
M
n
6
K
n
4
K
n
4
C02
n
3
C05
n
3
M
n
2
00
n
12
z
..37
C03
an
12
Response Comments
0210
M
00a00x
O
M
K
K
M
O
M
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 27-48
POSLine ISO8583 Interface Specifications
38
39
41
42
43
45
48
49
52
53
54
55
60
61
62
63
64
3.4.
Auth. Id. Response
Response Code
Terminal Id
Card Acq. Id
Card Acq. Name
Track 1 Data
Add. Data - Private
Currency Code
PIN Data
Security Control Info
Additional Amounts
ICC Related data
Private Use
Product Codes
Invoice/ECR Ref. #
Additional Data
Message Auth. Code
an
an
ans
ans
ans
ans
ans
n
b
n
an
b
ans
ans
ans
ans
b
6
2
8
15
40
..76
...999
3
64
16
...120
...255
...999
...999
...999
...999
64
M
M
O
M
M
C03
C
O
O
O
C07
O
K
O
O
O
O
In case of multi-currency processing (Option 2)
O
Use is application dependant
O
K
O
O
Refund
Bit Data Element Name
Message Type Id
Bit Map
02 Primary Acct Num.
03 Processing Code
04 Amount, Trans.
11 Systems Trace No
12 Time, Local Trans.
13 Date, Local Trans.
14 Date, Expiration
22 POS Entry Mode
24 NII
25 POS Condition Code
28 Fee Amount
35 Track 2 Data
37 Retrieval Ref No.
38 Auth. Id. Response
39 Response Code
41 Terminal Id
42 Card Acq. Id
43 Card Acq. Name
45 Track 1 Data
48 Add. Data - Private
49 Currency Code
52 PIN Data
53 Security Control Info
54 Additional Amounts
55 ICC Related data
60 Private Use
61 Product Codes
62 Invoice/ECR Ref. #
Attribute Request
n
4
0200
b
64
M
n
..19
C01
n
6 20a00x
n
12
M
n
6
M
n
6
K
n
4
K
n
4
C02
n
3
C05
n
3
M
n
2
00
n
12
z
..37
C03
an
12
an
6
an
2
ans
8
M
ans
15
M
ans
40
ans ..76
C03
ans ...999
n
3
C
b
64
O
n
16
O
an ...120
b ...255
C07
ans ...999
ans ...999
O
ans ...999
K
Response Comments
0210
M
20a00x
O
M
K
K
M
O
M
O
M
M
O
O
In case of multi-currency processing (Option 2)
O
Use is application dependant
O
K
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 28-48
POSLine ISO8583 Interface Specifications
63 Additional Data
64 Message Auth. Code
3.5.
O
O
O
O
Cash
Bit Data Element Name
Message Type Id
Bit Map
02 Primary Acct Num.
03 Processing Code
04 Amount, Trans.
11 Systems Trace No
12 Time, Local Trans.
13 Date, Local Trans.
14 Date, Expiration
22 POS Entry Mode
24 NII
25 POS Condition Code
28 Fee Amount
35 Track 2 Data
37 Retrieval Ref No.
38 Auth. Id. Response
39 Response Code
41 Terminal Id
42 Card Acq. Id
43 Card Acq. Name
45 Track 1 Data
48 Add. Data - Private
49 Currency Code
52 PIN Data
53 Security Control Info
54 Additional Amounts
55 ICC Related data
60 Private Use
61 Product Codes
62 Invoice/ECR Ref. #
63 Additional Data
64 Message Auth. Code
3.6.
ans ...999
b
64
Attribute Request
n
4
0200
b
64
M
n
..19
C01
n
6 01a00x
n
12
M
n
6
M
n
6
K
n
4
K
n
4
C02
n
3
C05
n
3
M
n
2
00
n
12
z
..37
C03
an
12
an
6
an
2
ans
8
M
ans
15
M
ans
40
ans ..76
C03
ans ...999
n
3
C
b
64
O
n
16
O
an ...120
b ...255
C07
ans ...999
ans ...999
O
ans ...999
K
ans ...999
O
b
64
O
Response Comments
0210
M
Attribute Request
n
4
0200
b
64
M
n
..19
C01
n
6 09a00x
n
12
M
n
6
M
n
6
K
n
4
K
n
4
C02
Response Comments
0210
M
01a00x
O
M
K
K
M
O
M
O
M
M
O
O
In case of multi-currency processing (Option 2)
O
Use is application dependant
O
K
O
O
Sale & Cash
Bit Data Element Name
Message Type Id
Bit Map
02 Primary Acct Num.
03 Processing Code
04 Amount, Trans.
11 Systems Trace No
12 Time, Local Trans.
13 Date, Local Trans.
14 Date, Expiration
09a00x
O
M
K
K
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 29-48
POSLine ISO8583 Interface Specifications
22
24
25
28
35
37
38
39
41
42
43
45
48
49
52
53
54
55
60
61
62
63
64
POS Entry Mode
NII
POS Condition Code
Fee Amount
Track 2 Data
Retrieval Ref No.
Auth. Id. Response
Response Code
Terminal Id
Card Acq. Id
Card Acq. Name
Track 1 Data
Add. Data - Private
Currency Code
PIN Data
Security Control Info
Additional Amounts
ICC Related data
Private Use
Product Codes
Invoice/ECR Ref. #
Additional Data
Message Auth. Code
n
n
n
n
z
an
an
an
ans
ans
ans
ans
ans
n
b
n
an
b
ans
ans
ans
ans
b
3
3
2
12
..37
12
6
2
8
15
40
..76
...999
3
64
16
...120
...255
...999
...999
...999
...999
64
C05
M
00
M
O
C03
M
M
M
O
M
M
C03
C
O
O
M
C07
O
K
O
O
O
O
O
In case of multi-currency processing (Option 2)
Use is application dependant
Contains cash component of transaction
O
K
O
O
3.7.
Off-line Sale
Offline Sale to $0.00 implies a reversed offline sale acknowledgement
Bit Data Element Name
Message Type Id
Bit Map
02 Primary Acct Num.
03 Processing Code
04 Amount, Trans.
11 Systems Trace No
12 Time, Local Trans.
13 Date, Local Trans.
14 Date, Expiration
22 POS Entry Mode
24 NII
25 POS Condition Code
35 Track 2 Data
37 Retrieval Ref No.
38 Auth. Id. Response
39 Response Code
41 Terminal Id
42 Card Acq. Id
43 Card Acq. Name
45 Track 1 Data
48 Add. Data - Private
Attribute Request
n
4
0220
b
64
M
n
..19
C06
n
6 00a00x
n
12
M
n
6
M
n
6
K
n
4
K
n
4
C06
n
3
C05
n
3
M
n
2
00
z
..37
an
12
an
6
M
an
2
ans
8
M
ans
15
M
ans
40
ans ..76
ans ...999
Response Comments
0230
M
00a00x
O
M
K
K
M
M
M
M
Host should always send „00‟ response code
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 30-48
POSLine ISO8583 Interface Specifications
49
52
53
54
55
60
61
62
63
64
3.8.
Currency Code
PIN Data
Security Control Info
Additional Amounts
ICC Related data
Private Use
Product Codes
Invoice/ECR Ref. #
Additional Data
Message Auth. Code
n
b
n
an
b
ans
ans
ans
ans
b
3
64
16
...120
...255
...999
...999
...999
...999
64
C
O
In case of multi-currency processing (Option 2)
O
O
Use is application dependant
C07
O
O
K
O
O
K
O
O
Off-line Refund
Bit Data Element Name
Message Type Id
Bit Map
02 Primary Acct Num.
03 Processing Code
04 Amount, Trans.
11 Systems Trace No
12 Time, Local Trans.
13 Date, Local Trans.
14 Date, Expiration
22 POS Entry Mode
24 NII
25 POS Condition Code
35 Track 2 Data
37 Retrieval Ref No.
38 Auth. Id. Response
39 Response Code
41 Terminal Id
42 Card Acq. Id
43 Card Acq. Name
45 Track 1 Data
48 Add. Data - Private
49 Currency Code
52 PIN Data
53 Security Control Info
54 Additional Amounts
55 ICC Related data
60 Private Use
61 Product Codes
62 Invoice/ECR Ref. #
63 Additional Data
64 Message Auth. Code
Attribute Request
n
4
0220
b
64
M
n
..19
C06
n
6 20a00x
n
12
M
n
6
M
n
6
K
n
4
K
n
4
C06
n
3
C05
n
3
M
n
2
00
z
..37
an
12
an
6
M
an
2
ans
8
M
ans
15
M
ans
40
ans ..76
ans ...999
n
3
C
b
64
n
16
O
an ...120
b ...255
C07
ans ...999
ans ...999
O
ans ...999
K
ans ...999
O
b
64
O
Response Comments
0230
M
20a00x
O
M
K
K
M
M
M
M
Host should always send „00‟ response code
O
In case of multi-currency processing (Option 2)
O
Use is application dependant
O
K
O
O
3.9.
Adjust, Sale
An adjustment to $0.00 implies a void transaction.
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 31-48
POSLine ISO8583 Interface Specifications
Bit Data Element Name
Message Type Id
Bit Map
02 Primary Acct Num.
03 Processing Code
04 Amount, Trans.
11 Systems Trace No
12 Time, Local Trans.
13 Date, Local Trans.
14 Date, Expiration
22 POS Entry Mode
24 NII
25 POS Condition Code
35 Track 2 Data
37 Retrieval Ref No.
38 Auth. Id. Response
39 Response Code
41 Terminal Id
42 Card Acq. Id
43 Card Acq. Name
45 Track 1 Data
48 Add. Data - Private
49 Currency Code
52 PIN Data
53 Security Control Info
54 Additional Amounts
55 ICC Related data
60 Original Amount
61 Product Codes
62 Invoice/ECR Ref. #
63 Additional Data
64 Message Auth. Code
Attribute Request
n
4
0220
b
64
M
n
..19
C06
n
6 02a00x
n
12
M
n
6
M
n
6
K
n
4
K
n
4
C06
n
3
C05
n
3
M
n
2
00
z
..37
an
12
M
an
6
M
an
2
M
ans
8
M
ans
15
M
ans
40
ans ..76
ans ...999
n
3
C
b
64
n
16
O
an ...120
O
b ...255
C07
ans ...999
O
ans ...999
O
ans ...999
K
ans ...999
O
b
64
O
Response Comments
0230
M
02a00x
O
M
K
K
New transaction amount after adjustment
M
M
Request contains original retrieval reference no.
M
M
Host should always send „00‟ response code
O
In case of multi-currency processing (Option 2)
O
Use is application dependant
O
Original amount before adjustment or void
K
O
O
3.10. Adjust, Credit
An adjustment to $0.00 implies a void transaction.
Bit Data Element Name
Message Type Id
Bit Map
02 Primary Acct Num.
03 Processing Code
04 Amount, Trans.
11 Systems Trace No
12 Time, Local Trans.
13 Date, Local Trans.
14 Date, Expiration
22 POS Entry Mode
24 NII
25 POS Condition Code
Attribute Request
n
4
0220
b
64
M
n
..19
C06
n
6 22a00x
n
12
M
n
6
M
n
6
K
n
4
K
n
4
C06
n
3
C05
n
3
M
n
2
00
Response Comments
0230
M
22a00x
O
M
K
K
M
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 32-48
POSLine ISO8583 Interface Specifications
35
37
38
39
41
42
43
45
48
49
52
53
54
55
60
61
62
63
64
Track 2 Data
Retrieval Ref No.
Auth. Id. Response
Response Code
Terminal Id
Card Acq. Id
Card Acq. Name
Track 1 Data
Add. Data - Private
Currency Code
PIN Data
Security Control Info
Additional Amounts
ICC Related data
Original Amount
Product Codes
Invoice/ECR Ref. #
Additional Data
Message Auth. Code
z
an
an
an
ans
ans
ans
ans
ans
n
b
n
an
b
ans
ans
ans
ans
b
..37
12
6
2
8
15
40
..76
...999
3
64
16
...120
...255
...999
...999
...999
...999
64
M
M
M
M
M
M
Request contains original retrieval reference no.
M
M
Host should always send „00‟ response code
C
O
In case of multi-currency processing (Option 2)
O
O
C07
O
O
K
O
O
O
Use is application dependant
O
Original amount before adjustment or void
K
O
O
3.11. Void, Sale
The Void transaction is used to inform the host that a transaction previously performed at the terminal has
been canceled.
Bit Data Element Name Attribute Request Response Comments
Message Type Id
n
4
0200
0210
Bit Map
b
64
M
M
02 Primary Acct Num.
n
..19
C06
03 Processing Code
n
6 02a00x
02a00x
04 Amount, Trans.
n
12
M
O
11 Systems Trace No
n
6
M
M
12 Time, Local Trans.
n
6
K
K
Request contains original transaction time
13 Date, Local Trans.
n
4
K
K
Request contains original transaction date
14 Date, Expiration
n
4
C06
22 POS Entry Mode
n
3
C05
24 NII
n
3
M
M
25 POS Condition Code n
2
00
35 Track 2 Data
z
..37
37 Retrieval Ref No.
an
12
M
M
Request contains original retrieval reference no.
38 Auth. Id. Response
an
6
O
39 Response Code
an
2
M
41 Terminal Id
ans
8
M
M
42 Card Acq. Id
ans
15
M
43 Card Acq. Name
ans
40
45 Track 1 Data
ans ..76
48 Add. Data - Private
ans ...999
O
49 Currency Code
n
3
C
O
In case of multi-currency processing (Option 2)
52 PIN Data
b
64
O
53 Security Control Info n
16
O
O
Use is application dependant
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 33-48
POSLine ISO8583 Interface Specifications
54
55
60
61
62
63
64
Additional Amounts
ICC Related data
Original Amount
Product Codes
Invoice/ECR Ref. #
Additional Data
Message Auth. Code
an
b
ans
ans
ans
ans
b
...120
...255
...999
...999
...999
...999
64
C07
O
O
K
O
O
O
Original amount before void.
K
O
O
3.12. Void, Credit
The Void transaction is used to inform the host that a transaction previously performed at the terminal has
been canceled.
Bit Data Element Name
Message Type Id
Bit Map
02 Primary Acct Num.
03 Processing Code
04 Amount, Trans.
11 Systems Trace No
12 Time, Local Trans.
13 Date, Local Trans.
14 Date, Expiration
22 POS Entry Mode
24 NII
25 POS Condition Code
35 Track 2 Data
37 Retrieval Ref No.
38 Auth. Id. Response
39 Response Code
41 Terminal Id
42 Card Acq. Id
43 Card Acq. Name
45 Track 1 Data
48 Add. Data - Private
49 Currency Code
52 PIN Data
53 Security Control Info
54 Additional Amounts
55 ICC Related data
60 Original Amount
61 Product Codes
62 Invoice/ECR Ref. #
63 Additional Data
64 Message Auth. Code
Attribute Request
n
4
0200
b
64
M
n
..19
C06
n
6 22a00x
n
12
M
n
6
M
n
6
K
n
4
K
n
4
C06
n
3
C05
n
3
M
n
2
00
z
..37
an
12
M
an
6
an
2
ans
8
M
ans
15
M
ans
40
ans ..76
ans ...999
n
3
C
b
64
O
n
16
O
an ...120
b ...255
C07
ans ...999
O
ans ...999
O
ans ...999
K
ans ...999
O
b
64
O
Response Comments
0210
M
22a00x
O
M
K
K
Request contains original transaction time
Request contains original transaction date
M
M
O
M
M
Request contains original retrieval reference no.
O
O
In case of multi-currency processing (Option 2)
O
Use is application dependant
O
Original amount before void.
K
O
O
Request Contains original ECR
3.13. Reversal
The Reversal message is sent if the terminal sent a transaction request into the network, and did not receive
a valid response before the transaction time-out period expired.
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 34-48
POSLine ISO8583 Interface Specifications
The reversal is sent persistently until a valid response to the reversal is received from the host.
Reversals will only be sent for on-line financial transaction messages.
Bit Data Element Name
Message Type Id
Bit Map
02 Primary Acct Num.
03 Processing Code
04 Amount, Trans.
11 Systems Trace No
12 Time, Local Trans.
13 Date, Local Trans.
14 Date, Expiration
22 POS Entry Mode
24 NII
25 POS Condition Code
35 Track 2 Data
37 Retrieval Ref No.
38 Auth. Id. Response
39 Response Code
41 Terminal Id
42 Card Acq. Id
43 Card Acq. Name
45 Track 1 Data
48 Add. Data - Private
49 Currency Code
52 PIN Data
53 Security Control Info
54 Additional Amounts
55 ICC Related data
60 Private Use
61 Product Codes
62 Invoice/ECR Ref. #
63 Additional Data
64 Message Auth. Code
3.14.
Attribute Request
n
4
0400
b
64
M
n
..19
C01
n
6
M
n
12
M
n
6
M
n
6
K
n
4
K
n
4
C02
n
3
C05
n
3
M
n
2
M
z
..37
C03
an
12
an
6
an
2
ans
8
M
ans
15
M
ans
40
ans ..76
C03
ans ...999
n
3
C
b
64
O
n
16
O
an ...120
b ...255
C07
ans ...999
ans ...999
O
ans ...999
K
ans ...999
O
b
64
O
Response Comments
0410
M
M
O
M
K
K
Same as original processing code
Same as original
Same as original
M
M
O
M
M
Host should always send „00‟ response code
O
In case of multi-currency processing (Option 2)
O
Use is application dependant
O
K
O
O
Same as original
Test Transaction
Bit Data Element Name Attribute Request Response Comments
Message Type Id
n
4
0800
0810
Bit Map
b
64
M
M
02 Primary Acct Num.
n
..19
03 Processing Code
n
6 99000x
99000x
04 Amount, Trans.
n
12
11 Systems Trace No
n
6
12 Time, Local Trans.
n
6
M
13 Date, Local Trans.
n
4
M
14 Date, Expiration
n
4
22 POS Entry Mode
n
3
24 NII
n
3
M
M
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 35-48
POSLine ISO8583 Interface Specifications
25
35
37
38
39
41
42
43
45
48
52
53
54
60
61
62
63
64
POS Condition Code
Track 2 Data
Retrieval Ref No.
Auth. Id. Response
Response Code
Terminal Id
Card Acq. Id
Card Acq. Name
Track 1 Data
Add. Data - Private
PIN Data
Security Control Info
Additional Amounts
Private Use
Private Use
Private Use
Private Use
Message Auth. Code
n
z
an
an
an
ans
ans
ans
ans
ans
b
n
an
ans
ans
ans
ans
b
2
..37
12
6
2
8
15
40
..76
...999
64
16
...120
...999
...999
...999
...999
64
M
O
M
O
O
O
O
Use is application dependant
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 36-48
POSLine ISO8583 Interface Specifications
3.15. Please Wait Advice
This is an unsolicited Host message that causes the terminal to display „Please Wait‟ and to extend its
transaction time-out. There is no corresponding request message for the please wait response.
Bit Data Element Name
Message Type Id
Bit Map
02 Primary Acct Num.
03 Processing Code
04 Amount, Trans.
11 Systems Trace No
12 Time, Local Trans.
13 Date, Local Trans.
14 Date, Expiration
22 POS Entry Mode
24 NII
25 POS Condition Code
35 Track 2 Data
37 Retrieval Ref No.
38 Auth. Id. Response
39 Response Code
41 Terminal Id
42 Card Acq. Id
43 Card Acq. Name
45 Track 1 Data
48 Add. Data - Private
52 PIN Data
53 Security Control Info
54 Additional Amounts
60 Private Use
61 Private Use
62 Private Use
63 Private Use
64 Message Auth. Code
3.16.
Attribute Request
n
4
b
64
n
..19
n
6
n
12
n
6
n
6
n
4
n
4
n
3
n
3
n
2
z
..37
an
12
an
6
an
2
ans
8
ans
15
ans
40
ans ..76
ans ...999
b
64
n
16
an ...120
ans ...999
ans ...999
ans ...999
ans ...999
b
64
Response Comments
0830
M
Attribute Request
n
4
0500
b
64
M
n
..19
n
6 92000x
n
12
n
6
M
n
6
n
4
n
4
n
3
n
3
M
Response Comments
0510
M
900001
M
M
M
O
Use is application dependant
Settlement
Bit Data Element Name
Message Type Id
Bit Map
02 Primary Acct Num.
03 Processing Code
04 Amount, Trans.
11 Systems Trace No
12 Time, Local Trans.
13 Date, Local Trans.
14 Date, Expiration
22 POS Entry Mode
24 NII
92000x
M
M
M
M
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 37-48
POSLine ISO8583 Interface Specifications
25
35
37
38
39
41
42
43
45
48
52
53
54
60
61
62
63
64
POS Condition Code
Track 2 Data
Retrieval Ref No.
Auth. Id. Response
Response Code
Terminal Id
Card Acq. Id
Card Acq. Name
Track 1 Data
Add. Data - Private
PIN Data
Security Control Info
Additional Amounts
Batch Number
Private Use
Private Use
Totals/Resp Text
Message Auth. Code
n
z
an
an
an
ans
ans
ans
ans
ans
b
n
an
ans
ans
ans
ans
b
2
..37
12
6
2
8
15
40
..76
...999
64
16
...120
...999
...999
...999
...999
64
M
M
M
M
M
O
O
O
M
M
O
Use is application dependant
Settlement batch number
O
O
Host response text is returned
3.17. Settlement Trailer
If the host requests the terminal to upload its batch, the terminal sends the settlement trailer following the
upload.
Bit Data Element Name Attribute Request Response Comments
Message Type Id
n
4
0500
0510
Bit Map
b
64
M
M
02 Primary Acct Num.
n
..19
03 Processing Code
n
6 96000x
96000x
04 Amount, Trans.
n
12
11 Systems Trace No
n
6
M
M
12 Time, Local Trans.
n
6
M
13 Date, Local Trans.
n
4
M
14 Date, Expiration
n
4
22 POS Entry Mode
n
3
24 NII
n
3
M
M
25 POS Condition Code n
2
35 Track 2 Data
z
..37
37 Retrieval Ref No.
an
12
M
38 Auth. Id. Response
an
6
39 Response Code
an
2
M
41 Terminal Id
ans
8
M
M
42 Card Acq. Id
ans
15
M
43 Card Acq. Name
ans
40
45 Track 1 Data
ans ..76
48 Add. Data - Private
ans ...999
O
52 PIN Data
b
64
53 Security Control Info n
16
O
O
Use is application dependant
54 Additional Amounts an ...120
60 Batch Number
ans ...999
M
Settlement batch number
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 38-48
POSLine ISO8583 Interface Specifications
61
62
63
64
Private Use
Private Use
Totals/Resp Text
Message Auth. Code
ans ...999
ans ...999
ans ...999
b
64
M
O
O
O
Host response text is returned
3.18. Batch Upload
This is the transaction set used to perform a batch up load. This occurs when the terminal and host are out
of balance or store and forward configuration.
Bit Data Element Name
Message Type Id
Bit Map
02 Primary Acct Num.
03 Processing Code
04 Amount, Trans.
11 Systems Trace No
12 Time, Local Trans.
13 Date, Local Trans.
14 Date, Expiration
22 POS Entry Mode
24 NII
25 POS Condition Code
35 Track 2 Data
37 Retrieval Ref No.
38 Auth. Id. Response
39 Response Code
41 Terminal Id
42 Card Acq. Id
43 Card Acq. Name
45 Track 1 Data
49 Currency Code
52 PIN Data
53 Security Control Info
54 Additional Amounts
55 ICC Related data
60 Original Data
61 Product Codes
62 Invoice/ECR Ref. #
63 Additional Data
64 Message Auth. Code
Attribute Request
n
4
0320
b
64
M
n
..19
C06
n
6
M
n
12
M
n
6
M
n
6
K
n
4
K
n
4
C06
n
3
M
n
3
M
n
2
M
z
..37
an
12
M
an
6
O
an
2
O
ans
8
M
ans
15
M
ans
40
ans ..76
n
3
C
b
64
n
16
O
an ...120
O
b ...255
C07
ans ...999
O
ans ...999
O
ans ...999
K
ans ...999
O
b
64
O
Response Comments
0330
M
M
O
M
K
K
Same as original transaction
M
M
M
If original response code is not present, assume „00‟
O
In case of multi-currency processing (Option 2)
O
Use is application dependant
O
K
O
O
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 39-48
POSLine ISO8583 Interface Specifications
4. Message Flows
4.1.
MESSAGE TYPE:
0100
POSLINE
0100
POS
Terminal
0100
Not Data Capture
0110
0110
4.2.
MESSAGE TYPE:
0200
POS
Terminal
0200
POSLINE
0100
BASE I
Data Capture
0210
4.3.
BASE I
MESSAGE TYPE:
0200
0110
0200 - REFUND
POSLINE
BASE I
POS
Terminal
Data Capture
0210
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 40-48
POSLine ISO8583 Interface Specifications
4.4.
MESSAGE TYPE:
0200
0200 - VOID REFUND
POSLINE
BASE I
POS
Terminal
Data Capture
0210
4.5.
MESSAGE TYPE:
0100
0200 - VOID SALE
POSLINE
0400
BASE I
POS
Terminal
Data Capture
0110
4.6.
MESSAGE TYPE:
0220
POS
Terminal
0410
0220
POSLINE
Data Capture
BASE I
0230
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 41-48
POSLine ISO8583 Interface Specifications
4.7.
MESSAGE TYPE:
0400
POS
Terminal
0400 - REVERSAL
POSLINE
Data Capture - Response is “00”
MESSAGE TYPE:
0500
POS
Terminal
BASE I
0410
0410
4.8.
0400
0500 - SETTLEMENT
POSLINE
BASE I
Not Data Capture
0510
4.9.
MESSAGE TYPE:
0320
0320 - BATCH UPLOAD
POSLINE
BASE I
POS
Terminal
Data Capture
0330
4.10.
MESSAGE TYPE:
0800
0800
POSLINE
BASE I
POS
Terminal
Not Data Capture
0810
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 42-48
POSLine ISO8583 Interface Specifications
4.11.
MESSAGE TYPE:
0830
POSLINE
BASE I
POS
Terminal
Not Data Capture, initiated by
Interface
0830
5. Settlement Process Flow
The terminal contains all the financial transactions expected to be settled. The terminal will ensure all unresolved advices are
sent to the host prior to the settlement transaction. This is done to ensure the hosts batch is up to date and in balance when the
transaction is received.
5.1.
Balanced Settlement
0500
POSLINE
POS
Terminal
0510
5.2.
Balanced Settlement With Advices
All unresolved advices are sent up to the host after the user settles to the terminal and before the settlement transaction is
sent.
0220
POS
Terminal
POSLINE
0230
…
0500
0510
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 43-48
POSLine ISO8583 Interface Specifications
5.3.
Out Of Balance Settlement
If the Host can not reconcile with the Totals received in the 0500 message of the terminal then it will
respond with Response Code 95. Then the Terminal should start to upload the financial transactions using
0320 messages. Host will respond to them with the 0330 message and the terminal should wait for the
response before sending the next 0320. After all of the financial transactions are uploaded, the terminal
should send a new 0500 message with processing code starting with 96.
If the Host still can not reconcile with the Totals received in the new 0500 then the above sequence
should be repeated until Host is able to reconcile. Host has to perform a successful reconciliation for
the transactions to be captured.
POS
Terminal
0500
0510 (95)
POSLINE
Processing Code:
 92 00 0x (Sett. Request)
 Response Code=95
0320
0330
…
0500
Processing Code:
 96 00 0x (Sett. Request)
 Response Code=00
0510
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 44-48
POSLine ISO8583 Interface Specifications
5.4.
Balanced Settlement Or Batch Upload Time Out
When a Settlement Request (0500) times out the terminal will not allow the batch to be changed in any matter and the
only functionality available should be to repeat the settlement.
When a Batch Upload Request (0320) times out the terminal will not allow the batch to be changed in any matter and
the only functionality available should be to repeat the settlement.
5.5.
Delayed Settlement
If the Host after it receives the Settlement Request (0500), it detects that the Reconciliation will take more time than the
Timeout of the Terminal, it will send an unsolicited “Please Wait Advice” (0830). On ce the Terminal receives this message,
it should restart its internal timer providing to the Host some more time to respond to the reconciliation message before the
Terminal times out.
The Host may repeat the 0830 message up to a specific number of times. If the Reconciliation process in not even in a
specific time, Host will respond with 91 in the Reconciliation respond.
POS
Terminal
0500
POSLINE
Processing Code:
 92 00 0x (Sett. Request)
0830
Delay Detected
0830
0510
Delay Detected
Processing Code:
 96 00 0x (Sett. Request)
 Response Code=00
6. Multicurrency Processing
6.1.
Option 1. Standard.
If Currency Code is not sent in the Request Message, the Host must use its database to decide on the Currency of the
transaction.
At the Host level, each Terminal ID can have only one Currency Code assigned.
Therefore, when the Multicurrency option is enabled at the Terminal Level, the Terminal must be sending a different
Terminal ID (field 41) for each currency that is supported by the Terminal software.
Settlement is also performed by Terminal ID so in this case, Multiple Settlements (one for each Currency) must be initiated
from the Terminal for the transactions to be captured.
In this case Field 63 format specified in Section 2.26.3.1 should be used.
6.2.
Option 2. Multi-currency merchant
If the same Merchant and Terminal ID are used with different currencies, Currency Code field should be presented in
Request Message.
In this case Field 63 format specified in Section 2.26.3.2 should be used.
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 45-48
POSLine ISO8583 Interface Specifications
7. Payment System Support
Payment System
VISA
VISA SMS
MasterCard
MDS
ONX
EuroPay
AMEX
Support







8. Installment Processing
When the Host receives an installment transaction, POSLINE verifies that the installment data are valid accordingly to
merchant‟s installment setup. If one of the installment checks fails, POSLINE responds with an error message. On the traffic
screen of POSLINE a message is displayed showing an error number, which corresponds to the description of why the
installment request was declined.
Errors returned by PHIM regarding installment requests:
Error Number
0
1
2
3
4
5
6
7
8
9
10
Description
Installment transactions not allowed for merchant
Installment request‟s loan period not set
Installment request‟s loan period not set equals to zero 0.
Installment request‟s loan period exceeds maximum allowed loan period for merchant
Installment request‟s loan period exceeds minimum allowed loan period for merchant.
Installment request‟s offset period exceeds maximum allowed offset period for merchant
Buy Now/Pay Later option not enable for merchant
Error during currency conversion
Monthly installment amount exceeds maximum monthly amount allowed for merchant
Monthly installment amount exceeds minimum monthly amount allowed for merchant
Installment request‟s transaction amount exceeds installment floor limit allowed for merchant.
0200
POS
Terminal
0210 (00)
POSLINE
 Field 63, set for installment
request
 Field 03, 00 x0 xx (Purchase)
 Response Code=00
0100
0110 (00)
BASE I


0200
0210 (12)
…

 Field 63, set for installment
request
 Field 03, 00 x0 xx (Purchase)
 Response Code=12
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Field 048, set
with installment
data
Field 03, 00 x0
xx (Purchase)
Response
Code=00
Page 46-48
POSLine ISO8583 Interface Specifications
9. OTB-Settlement Table
Transaction
Message Type
Authorisation
Pre-Authorisation
Balance Inquiry
Fee inquiry
Check Verification
Card Verification
Sale
Refund
Cash
Sale & Cash
Void, Sale, on-line
Void, Refund, on-line
Off-line Sale
Off-line Refund
Sales Completion
Adjust, Sale
(void off-line)
Adjust, Refund
(void off-line)
Off-line Sale with zero
amount (Reversed
Offline Sale,
Acknowledgement)
Guaranteed Late Arrival
Reversal
0100
Settlement Request
0500
0200
0220
0400
Settlement, after upload
Batch Down Line Load
Batch upload
0320
Processing
Code
00 a0 0x
30 a0 0x
31 a0 0x
32 a0 0x
04 a0 0x
38 a0 0x
00 a0 0x
20 a0 0x
01 a0 0x
09 a0 0x
02 a0 0x
22 a0 0x
00 a0 0x
20 a0 0x
00 a0 0x
02 a0 0x
OTB
change
(Send to
Issuer)
db
db
0
0
Db
Db
Db
Db
Cr
-
Settlement
(Included in
the EDC
file)
db
cr
db
db
cr
db
db
cr
db
db/cr
22 a0 0x
-
cr/db
00 a0 0x
-
-
cr/db
cr/db
-
Confirms
the
settlement
Confirms
the
settlement
for the
second time
db/cr
90 a0 0x
Same as
original
transaction
92 00 0x
96 00 0x
-
95 00 0x
Same as
original
-
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
02 July 2013
Page 47-48
POSLine ISO8583 Interface Specifications
Signature Data
Statistics
Logon
Initialisation
Test Transaction
Please Wait Advice
Features
1. Dual Currency Terminals
0320
0800
0830
transaction
90 00 0x
91 00 0x
92 00 0x
93 00 0x
99 00 0x
90 00 0x
-
Terminal ID
The POS Terminal must
be able to send a different
id for each currency
POSLine ISO8583 Specifications (ONLINE 4 12-12) v1.1.docx
-
Merchant ID
The POS Terminal must
be able to send a different
id for each currency
02 July 2013
Page 48-48