0% found this document useful (0 votes)
295 views31 pages

ISO 8583 Processing Code Overview

The document describes the structure and elements of an ISO 8583 message. An ISO 8583 message consists of an MTI (Message Type Identifier), primary and secondary bitmaps, and data fields. The most commonly used messages are authorization requests and responses, file updates, reversal notices, and network management messages. The document then defines the accepted data elements for processing ISO 8583 messages.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
295 views31 pages

ISO 8583 Processing Code Overview

The document describes the structure and elements of an ISO 8583 message. An ISO 8583 message consists of an MTI (Message Type Identifier), primary and secondary bitmaps, and data fields. The most commonly used messages are authorization requests and responses, file updates, reversal notices, and network management messages. The document then defines the accepted data elements for processing ISO 8583 messages.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

ISO 8583 Message

ISO8583 Manual
ISO 8583 Messaging

Message Structure:

MTI Bit Map Bit Map 2 3 4 1 1 1

MESSAGE TYPE IDENTIFIER (MTI) n 4 Bytes 001~004


The MTI is a four-digit numeric field that identifies each message by defining the type of
message, the function of the message and the origin of the transaction: All messages start with
an MTI.
Posición en MTI Descripción Values
1 Version Number 0 - ISO8583:1987
1 - ISO8583:1993
8 - Specials
2~9 - reserved values.
2 Tipo de Mensaje 0 - Reserved ISO
1 - Authorization
2 - Financial
3 - Blockages
4 - Reversions/Chargebacks
5 - Reconciliation
6 - Administrative
7 - Fee sets
8 - Network Administration
9 - Reserved ISO
3 Function of the message 0 - Request
1 - Request Response
2 - Advice
3 - Advice Response
4 - notification
5~9 Reserved ISO
4 Originating from the transaction 0 - Acquire
1 - Acquire repeat
2 - Card issuer
3 - Card issuer repeat
4 - other
5 - other Repeat
6–Reserved ISO
8~9 Reserved ISO

The highlighted values indicate the types of messages used by convention.

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page. 1


ISO 8583 Message

Messages Used by Convention

MTI Type of Message Description


0200 Authorization Request - For operations at POS, at ATM, E-
financial Commerce and Authorization Center
0210 Response to request for Response to 0200
Financial Authorization
0300 Update request for For card blocking
files
0310 Order response update Response to 0300
of files
0420 Reversion Notice Reversal (total or partial) of a transaction 0200
Notification of Refunds (Reversals) of the
previously described transactions
0430 Response to Reversion Notice Response to messages 0420

0800 Administration Request Message exchange between Switch and entities


Red (Sign-on and sign-off)
0810 Response to the request of Response to 0810
Network Administration

Definition of data elements


The following is the definition of the accepted data for processing the
messages.
All the detailed data below will be considered mandatory, therefore in
absence of data for a field, it must contain white characters or the number
zero (0).
The format in which the fields are presented is:

Field Name Number Type Size Format


field given (fixed or maximum)

The BIT MAPs (bitmap)


The Bit Map specifies which fields of ISO8583 are present and which are not. Each
Message has 2 Bit Maps: the Primary Bit Map and the Secondary Bit Map.

0 The Primary Bit Map b 8 Bytes


The primary Bit Map consists of 64 bits (8 bytes) located following the MTI, except for the first
bit, each bit is associated with a corresponding data field from 2 to 64.

The value of the bits determines when the data is present in the message:
- If a bit is 0 So the field associated with that bit is not present.
- If a bit is 1 Then the field associated with that bit is included in the message.
Data field number 1 does not exist, the first bit of the primary Bit Map is used to indicate the
presence of the secondary Bit Map.

1 The Secondary Bit Map b 8 Bytes


The secondary Bit Map is the same as the primary Bit Map, except that it is associated with the data fields.
ranging from 65 to 128. The Secondary Bit Map is included only if there is data in the
fields 65 to 128.

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 2


ISO 8583 message

2 PAN a (2+19) LLVAR


The Primary Account Number (PAN) is a series of digits used
to identify the customer's card number.

The length of the PAN is specified in the first two Bytes and can be from 1 to 19.
Subfield Position Description Attribute
1 01~02 Cant. of Data in LL
2 03~LL PAN a

Note: the message from 0800 of Network management must contain PAN BIN (Bank Institution
Number) for sign-on/off.

3 Processing Code n 6 Bytes


The processing code is a series of 6 digits that describes the effect of a transaction on
the customer's account and the types of accounts affected.
The values for field 3 are described in Annex I.

4 Transaction Amount n 12 Bytes


The transaction amount is the amount of funds that the cardholder requests.
There are 12 fixed positions with the last 2 decimal digits.

5 Settlement Amount n 12 Bytes


The reconciliation amount is the sum of funds that must be transferred between the Acquirer and the
entity. It is equal to the Amount Transaction in the settlement currency.

6 Cardholder Billing Amount n 12 Bytes


It is the amount that will be charged to the cardholder's account in the corresponding currency of
your account defined in the Cardholder Amount currency field 51.
There are 12 fixed positions with the last 2 decimal digits.

Note: If there are no data in field 6, the values to be considered are taken from field 4.

7 Transmission Date and Time n 10 Bytes MMDDhhmmss


Transmission Date and Time is the date and time when the message
enter the data exchange system. If the transaction comes from abroad, the date and the
now expressed in Greenwich Mean Time (GMT), unless it is the local date and time.
The data in this field must be valid dates and times.

Subfield Position Description Attribute


1 01~04 Date MMDD
2 05~10 Hour hhmmss

Where:
MM is the month: 1 <= MM <= 12
DD is the day: 1 <= DD <= 31
hh is the time: 0 <= hh <= 23
it is the minutes: 0 <= mm >= 59
these are the seconds: 0 <= ss >= 59

9 Settlement Conversion Rate n 8 Bytes


It is the factor used in the conversion of the amount in field 5 (Transaction Settlement Amount)
Therefore, Field5 = Field4 * Field9.
C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 3
ISO 8583 message

The first digit on the left determines the number of positions that the decimal separator must
be moved from the right.

6 9 9 7 2 5 2 3

Displacement
Exchange: 9.9972523

Example a field9 with the value 69972523


Indicates that the conversion rate is 9.972523
Note: The value of the first digit from the left must be between 0 and 7.

10 Cardholder Billing Conversion Rate n 8 Bytes


It is the factor used in the conversion of the amount in field 6 (Cardholder Billing Amount)
Therefore, Field6 = Field4 * Field10.

The first digit on the left determines the number of positions the decimal separator must be.
be moved from the right. Like field 9.
11 System Trace Audit Number n 6 Bytes
The STAN is a number that uniquely identifies the message. The value of the Trace
remains unchanged in all messages during the life of the transaction.
The STAN is generated by the originator of the message.

12 Local Transaction Time n 6 Bytes hhmmss


It is the local time at which the transaction takes place. By local, it is understood to mean the place where it is.
located the Acquirer of the transaction.
The data must contain hours(hh), minutes(mm), and seconds(ss)

13 Local Transaction Date n 4 Bytes MMDD


It is the local date on which the transaction is made. By local, we mean the place where it is.
located the Acquirer of the transaction.
The data must contain month (MM) and day (DD).

14 Date Expiration n 4 Bytes YYMM


Specify the year and month when the user's card expires.
The data must contain year (YY) and month (MM).

15 Settlement Date n 4 Bytes MMDD


It is the trade date, the date that will be used for the reconciliation of the involved accounts.
The data must contain month (MM) and day (DD)

16 Conversion Date n 4 Bytes MMDD


It is the date on which Fields 9 and 10 (conversion rate) are effective for converting the amount of
the transaction.
The data must contain month (MM) and day (DD)

18 Merchant Type n 4 Bytes


It is the business sector code.
El dato debe contener un valor valido de MCC (Merchant Category Code)

19 Acquiring Institution Country Code n 3 Bytes


Country Code of the acquiring institution.

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 4


Mensaje ISO 8583

20 Pan Country Code n 3 Bytes


Country code where the sender is located.

22 Point Of Service Entry Mode a 4 Bytes


POS Entry Mode consists of a numerical code to indicate how the transaction was processed,
what is the device used, etc.

Value
E-Commerce 5900

23 Card Sequence Number n 3 Bytes


Number to distinguish between separate cards with the same number or extended number.

24 Network International Identifier n 3 Bytes


It constitutes the Device Identifier associated with the Acquirer or the Forwarding
See Annex III a).

25 Point Of Service Condition Service a 4 Bytes


POS Condition service consists of a numerical code to describe how it was processed.
transaction, serves to distinguish a verification request from an authorization request.

Codigo Definición
00 Normal Transaction of this type
01 The client is not present
02 Terminal without attention e.g. ATM
03 Trade or suspicious card
05 Client Present, card absent
08 Mail Order / Telephone Order
10 Customer Identity Verified
51 Account verification request without authorization
55 Request for telecode authorization

26 PIN Data Length n 2 Bytes


Contains the length of the PIN entered by the User that is present in field 61.

28 Amount Transaction Fee n 12 Bytes


It is the amount charged for the transaction, expressed in the same currency code.
Transaction Amount.

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 5


ISO 8583 message

32 Acquiring Institution Id. Code a (2+11) LLVAR


Identify the Acquirer entity.

Subfield Position Description Attribute


1 01~02 Data Cant. in LLVAR
2 03~LL Id Code A

33 Forwarding Institution Id. Code a (2+11) LLVAR


Identify the entity from which the message originates in case it is not the same entity.
Acquirer of field 32.

Subfield Position Description Attribute


1 01~02 Data Cant. in LLVAR
2 03~LL Id Code a

34 Primary Account Number Extended n 3 Bytes


It is used to identify the Customer's account or its relationship with other accounts.

35 Track-2 Data a (2+37) LLVAR


It is the information found on the Track2 of the magnetic stripe of the card.
Track2 of the card
Subfield details
Length of Track2
Card Number
Separator field
Expiration date (YYMM)
Service Code
Discretionary data
This field contains registered data of the PVV and CVV.

Subfield Position Description Attribute


1 01~02 Data Count in LLVAR
2 03~LL Track2 A

37 Retrieval reference Number n 12 Bytes


It is a number that uniquely identifies the message. The value remains unchanged in
all messages during the life of the transaction.

38 Approval Code a 6 Bytes


Approval code granted by the entity to the transaction.
This data is only generated for approved transactions, and they are used again for the
Reversals or Refunds that may exist.

39 Response Code a 2 Bytes


Define the arrangement of a previous message.
Identify the reason for rejection, if any, or 00 for approved
Possible return codes in Annex II

40 Service Restriction Code n 3 Bytes

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 6


ISO 8583 Message

Identify the type of service by geographic region.

41 Card Acceptor Terminal Id a 8 Bytes


Identify unequivocally a terminal in the card acceptor

42 Card Acceptor Id Code n 15 Bytes


Establishment code of the transaction's origin, right-aligned, filled with zeros to
the left

43 Card Acceptor Name/Location a 40 Bytes


Data string that identifies the business. It can be name, address, etc.
The last two bytes must contain the country code. (in our case PY)

44 Additional Response Data a (2+99) LLVAR


Additional information for the Message Receiver. Includes additional information that, in the event of
problems in the message, inform which field is inconsistent or has issues. Likewise,
Also, in the case of multiple messages (such as the Extract), three bytes are sent.
of data (only for approved transactions)

Subfield Position Description Attribute


1 01~02 Data Count in LLVAR
2 03~05 Multiple Message Indicator N

For the case of Extracts that require more than one response message (MTI 0210), we
proceed as follows:
The initial value 001 is sent in the Additional Response Data.
The terminal will respond with a Financial Authorization Request message (MTI 0200) with the
the same value in field 44. If there is additional data, another MTI 0210 will be generated with the value
002 and so on. In case there are no more data, the value will be 000.

C:\Users\DESARROLLO\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Pág. 7


ISO 8583 Message

45 Track 1 Data a (2+76) LLVAR

It is the information found on Track 1 of the magnetic strip of the card.

Subfield Position Description Attribute


1 01~02 Data Canto in LLVAR
2 03~LL Track1 a

Track 1 of the card


Detail of subfields
Card Number
Separator field
Username
Separator field
Expiration date (YYMM)
Service Code
Discretionary data

47 Statement (Extract) a (3+980) LLLVAR

In this field, lines to be presented/printed are issued consecutively. Each line to be


processed is preceded by a 3-byte field that specifies its length

Subfield Length Description Attribute


1 003 Length of the 1st line n
2 Long Message for the first line Ticket a
3 003 Length of the 2nd line n
4 Long Message for the second line a
.. .. .. ..
n 003 Length of line n n
n Message for line n a

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 8


ISO 8583 Message

Servicios:
For services, this field contains the messages to be displayed on the Ticket in case of
that the transaction be approved

Subfield Position Description Attribute


1 001~003 Length of the line
2 004~043 Message for the POS user a 40 bytes
3 044~046 Length of the line
4 047~086 Message for the first line Ticket a 40 bytes
5 087~089 Length of the line
6 090~129 Message for the second line Ticket a 40 bytes
7 130~132 Length of the line
8 133~172 Message for the third line Ticket a 40 bytes
9 173~175 Length of the line
10 160~199 Message for the fourth line Ticket a 40 bytes

2 Message to the User a 40 Bytes

It is the message assigned by the Provider to the User.


If a transaction is denied with (Response Code 05), then the content of this field
It is displayed on the POS viewer.
If a transaction is approved (Response code 00), then the content of this field is
print at the bottom of the ticket.

4 Line 1 of the Ticket a 40 Bytes

6 Line 2 of the Ticket a 40 Bytes

8 Line 3 of the Ticket a 40 Bytes

10 Line 4 of the Ticket a 40 Bytes

It is for the Provider to customize the header of the Ticket

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 9


ISO 8583 Message

48 Additional Data a (3+255)

El campo de datos Adicionales es redefinido para contener los siguientes subcampos:

Subfield Position Description Attribute


1 001~001 Type of transaction a 1 byte
2 002~003 Number of installments in 2 bytes
3 004~018 Commercial code processor. to 15 bytes
4 019~033 Ballot Number a 15 bytes
5 034~036 CVV of the card in 3 bytes
6 037~037 CVV Entry Method in 1 byte
7 038~117 Service information a 80 bytes
8 118~119 Payment Type in 2 bytes
9 120~134 Payment method details a 15 bytes
10 135~142 Additional Data Debit Card in 8 bytes
11 143~144 Plan for Installments in 2 Bytes

Details of the subfields

Transaction type a 1 Byte 001~001


The type of transaction is defined through the TCC (Transaction Category Code) table.
Transaction codes (T.C.C. according to ISO).
See Annex III c).

2. Cantidad de cuotas n 2 Bytes 002~003


To specify the number of installments in which the transaction amount will be applied to the account
of the user.

3. Commercial code of the processor a 15 Bytes 004~018


It is the code assigned by other processors.

4. Ticket Number n 15 Bytes 019~033


It is the ticket number generated by the device

5. CVV2 of the Card n 3 Bytes 156~158


It is the CVV2 number that appears on the card printout. This security element for
the VISA brand is identified as CVV2 and for the Mastercard brand it is CVC2

6. CVV2 Entry Method n 1 Byte 159~159


Establish the way in which the CVV2 is sent
Possible values in Annex III d).

SERVICIOS:

For service transaction cases (Proc. Code = 900000), this field contains:
Service Data, Payment Type and Payment Type Data

[Link] Data a 80
Service Data is the transaction data of the service Whatever its origin,
entered, by magnetic stripe reading or by barcode reader reading, etc.

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 10


ISO 8583 message

Note: The first four digits determine the Identifier of the Provider or billing entity. In the case
from the mobile phones, the phone number (09X1nnnnnn) will appear followed by spaces in
white

8. Payment Type a 2 Bytes


Code of the payment type with which the operation was carried out.

TYPE OF PAYMENT CODE


Cash 00
Credit Card 01
Debit Card 02
Check 03
Others 04

9. Datos del Tipo de Pago a 15 Bytes


If the payment type is different from 00, then the following 15 Bytes contain information about
the payment for example Receipt number if the payment type is 01 or 02 and check number if the type
the payment is 03

10. Additional Data Debit Card n 8 Bytes


Contains additional data of the debit card that are necessary for its identification in the
Red. This data is mandatory in transactions where there was no reading of Track2.
card. The data structure is as follows:

Subfield Long Type.


Issuing Bank Code n 3
Card Currency n 1
Card Holder Number n 2
Card Issuance Number n 2

11. Installment Plan n 2 Bytes


Coding to implement different installment plans, associated with the number of installments that
go to sub-element 2.

49 Transaction Currency code n 3 Bytes


Specify the currency used in field 4 (Transaction Amount).
It is the local currency of the Acquirer, or in the source of the transaction.
Possible values in Annex III e).

50 Settlement Currency code n 3 Bytes


Specify the currency used in field 5 (Settlement Amount).
This field must have some value if there is data in field 5.

51 Cardholder Billing Currency code n 3 Bytes


Specify the currency used in field 6 (Cardholder Billing Amount).
This field must have some value if there is any data in field 6.

52 Pin Data b 8 Bytes [Link]


It is the encrypted PIN entered by the user

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 11


Mensaje ISO 8583

53 Security Related Information an 16 Bytes


Additional data related to the PIN entry method (Pin block, etc.)

54 Additional Amounts a (3+120) LLLVAR


In this field, the Switch must handle the Current Balance and Available Balance data and others.
additional balances.
It can handle up to 6 groups of 18 bytes each.
Each one divided into the following subfields

Subfield Type Can't. Bytes


Tipo de Cuenta n 2
Currency Code n 3
Debit/Credit a 1
Amount n 12

The possible values for account type are in Annex III f).
The value 00 in the Account Type subfield determines the balance of an unspecified account.
If the transaction is local, the positions from 004 to 021 contain the current balance and
Positions 022~039 the Available balance.
Positions 040~057 the Additional Balance 1.
The positions 058~075 the Additional balance 2.
Positions 076~093 the Additional balance 3.
Positions 094~111 the Additional balance 4.

The fields can then be:

Subfield Position Description Attribute


1 001~003 Data Cant. N LLLVAR
2 004~005 Account Type. N 2 Bytes
3 006~008 Cod. Moneda Saldo Actual N 3 Bytes
4 009~009 Debit/Credit Current Balance A 1 Byte (D=debit C=Credit)
5 010~021 Monto Saldo Actual N 12 Bytes
6 022~023 Account Type. Available Balance. N
7 024~026 Currency Code Available Balance N
8 027~027 Debit/Credit Available BalanceA
9 028~039 Amount Balance Available N
10 040-041 Tipo Cta N 2 Bytes
11 042-044 Cod. Moneda Saldo Adic. N 3 Bytes
12 045-045 Débito/Crédito Saldo Adic. A 1 Byte (D=debit C=Credit)
13 046-057 Additional Balance Amount N 12 Bytes
14...
15...
16....

55 Integrated Circuit Card Related Data a (3+255) LLLVAR


It contains data related to the information contained in the chip of the smart card.

59 Transport Data a (3+255) LLLVAR


Contains data from the Message Originator and must be returned unchanged in the message
of response.
C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 12
ISO 8583 Message

60 Advice Reason Code a (2+60) LLVAR


It is used to inform the recipient of the Advice about the specific reason for the issuance of the message.

61 POS. Data a (2+26) LLVAR


Service Point data are the data that indicate the conditions under which the processing was done.
transaction.

62 Intermediate Network Facility Data a (3+100) LLLVAR


It contains additional network information, used to facilitate and secure the sending of certain
messages.

63 Banknet Data a (3+600) LLLVAR


This field handles the Current Balance and Available Balance data.

64 Message Authentication Code b 8 Bytes


It is used to validate the source and the text of the message between the origin and destination of the message.

70 Network Management information code n 3 Bytes


This field is used in messages 08XX (0800 and 0810) and serves to identify the status of the
Red. See Annex III g)

73 Action Date n 6 Bytes MMDDYY


Specify the date of a future action. Eventually, it can be used to indicate a date.
as date of birth.

90 Original Data Element a 42 Bytes


This field is exclusive to reversal messages, where all elements can be found.
of data corresponding to the original message, in such a way as to identify the transaction to be
reverted or corrected.

Contains the following subfields:

Subcampo Posición Description Attribute


1 001~004 Original MTI n( 4 Bytes)
2 005~010 Original STAN n( 6 Bytes)
3 011~020 Original Trans. Date and Time MMDDhhmmss
4 021~031 Original Acquirer ID n( 11 Bytes)
5 032~042 Original Forwarding ID n( 11 Bytes)

Detail of the subfields

Original MTI n 4 Byte ["001","002","003","004"]


It is the Original message Identifier to which it refers.

Original STAN n 6 Byte 005~010


It is the value contained in field 11 of the message being referenced.

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 13


ISO 8583 Message

Original Transmission Date and Time n 10 Byte 011~020


It is the value contained in field 7 of the message to which it refers.

Original Acquirer Institution ID code n 11 Byte 021~031


It is the value contained in field 32 of the referenced message.

Original Forwarding Institution ID code n 11 Byte 032~042


It is the value contained in field 33 of the message to which it refers.

91 File Update Code n 1 Byte


Specify the action to be taken in the update of a given file.
The values are as follows:

Value Meaning
1 New Registration
2 Change Registration
3 Borrar Registro
5 Reading
8 Delete Record

92 File Security Code n 2 Byte


It is a security code that ensures the originator of the update message is
authorized to carry out the update of the file.

93 Response Indicator n 5 Bytes


Response to a request for issued update.

94 Service Indicator n 7 Bytes


Indicate the type of service supported by the file update message receiver. It is
used for coordination with the file update message.

95 Replacement Amount n 36 Bytes


Another exclusive area of the reversals, in it are the "new values" necessary
To carry out a partial or total reversal of the transaction to which the reversal refers.

Contains the following subfields:

Subfield Position Description Attribute


1 001-012 ( 12 ) Actual Transaction Amount n
2 013-024 ( 12 ) Actual Settlement Amount n
3 025-036 ( 12 ) Actual Cardholder Billing Amount n

Note: In cases of reversals for cash withdrawals at ATMs, certain situations may arise.
special situations, for the following reason:
At the initial request (0200), the issuing entity approved the transaction;
The ATM, when attempting to dispense the requested amount approved by the entity, detects a non-
availability of sufficient tickets for it, and proceeds to deliver up to what is available, this

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 14


Mensaje ISO 8583

The value of what is dispensed is the value that will be presented in the first subfield of field 95 Actual.
Transaction Amount

The entity must proceed according to one of the following options:

Reverse or refund the original order and make the new debit for the amount.
corresponding, which appears in the first subfield of field 95
b). Credit the customer's account with the amount of the difference between what was authorized in the
original message 0210 and what is actually dispensed by the cashier that appears in the subfield
Actual Transaction Amount (field 95 of message 0420)

96 Message Security Code a 32 Bytes


It is used for the transmission of encrypted keys or key validation values.

100 Receiving Institution Identification Code a (2+11) LLVAR


Identify the receiving Institution of the Transaction. It is used in case the identifier of the
the issuing entity is not the same as that listed on the PAN.

101 Message Data Element a (2+17) LLVAR


Specify the name or abbreviation of the file being accessed.

102 Account 1 n 28 Bytes


In this field goes the customer's account.
This field is a fixed size of 28 bytes in which the account type, the currency, and
the account number of it according to the following scheme

Subfield Type Cant. Bytes


Tipo de Cuenta n 2
Currency Code n 3
Account Number n 23

103 Count 2 n 28 Bytes


This field is used when transactions of fund transfer are carried out.
This field is of fixed size of 28 bytes in which the account type, the currency and
the account number of the same according to the following scheme

Subfield Type Cant. Bytes


Tipo de Cuenta n 2
Currency Code n 3
Account Number n 23

118 Intracountry Data a 103 LLLVAR


Data for local exchange.

120 Record Data a (3+500) LLLVAR


Variable-length field, in free format, used to transmit records or messages in
text format.

C:\Users\DESARROLLO\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 15


ISO 8583 Message

121 Authorizing Agent Identification Code a (2+11) LLVAR


Code that identifies the transaction authorizer.

122 Private for National Use (3+100) LLLVAR


For the private use of the User

126 Vector Account Selection OAR a (3+280) LLLVAR


In case the user has more than one account associated with a card, this field will go
all user accounts in fixed fields of 28 bytes each following the next
structure:

Subfield Type Cant. Bytes


Tipo de Cuenta n 2
Currency Code n 3
Account Number n 23

The value of the LLL must be a multiple of 28.


The possible values for account type are in Annex III f).

127 Blocking Data a 122 Bytes


ISO determines this field for private data and redefines it to contain data
from the card blocking in a message 0300 and 0310

Subfield Position Description Attribute


1 001~002 Lock Code (2 bytes) n (2 bytes)
2 003~012 User ID a (10 bytes)
3 013~022 System ID (operator) a (10 bytes)
4 023~122 Block Message a (100 bytes)

Detail of the subfields

Blocking Code n 2 Bytes 001~002


It is a field that is two bytes long, containing numeric data.
See Annex III h)

ID de Usuario a 10 Bytes 003~012


It is an alphanumeric field, with alphabetic data ten bytes long.

It is a field where the name of the operator of the Authorization Center is reported.
enabled to perform card blockages from our computer. It cannot be omitted in
the cases of blockages.

System ID (operator) a 10 Bytes 013~022


The name of the computer on which the blocking request is made.

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 16


ISO 8583 message

Blocking Message a 100 Bytes 023~122


Additional comments on the card blocking.

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 17


ISO 8583 Message

Annex I
Processing Code Operation Code Field 3 (6 Bytes)

Operation Count Code


Cash withdrawal ATMs Cta. Universal 010000
“ “ C.C. 012000
“ “ C.A. 011000
“ “ Republic of Turkey 013000
Purchases at POS --------- 000000
“ “ --------- 003000
“ “ Selective 001000
“ “ the same 002000
Cash Deposits Universal 210000
“ ” C.C. 210020
“ “ C.A. 210010
Deposit Check with the same Bank. Ct. Universal 210001
“ “ “ “ C.C. 210021
“ “ “ “ C.A. 210011
Deposit Cheque with other Banks. Cta. Universal 210002
C.C. 210022
“ “ “ “ C.A. 210012
Transfer funds between C.C. and C.A. 402010
Customer Accounts > C.C. to C.C. 402020
“ “ C.A. to C.A. 401010
“ “ C.A. to C.C. 401020
“ “ C.C. to T.C. 402030
“ “ C.A. to T.C. 401030
Payment Services Cta. Universal 900000
“ “ C.A. 901020
“ “ C.C. 902020
Payment Services (Debit Credit Cash) ----------- 900000
Payment of Credit T. ----------- 500030
Request for Extracts Universal Cta. 510000
C.C. 512000
C.A. 511000
Republic of Turkey 513000
Undetermined requests 560000
Balance Inquiry Cta. Universal 310000
“ ” C.C. 312000
“ “ C.A. 311000
“ “ Republic of Turkey 313000

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 18


ISO 8583 Message

Annex II
Response Code Field 39 (2 Bytes)
Code Description of the return code
00 Transaction accepted
01 Call the issuing entity
02 Contact the card issuer
03 Invalid trade
04 Capture the card
05 Do not accept the card
06 Error
07 Capture the card - Possible fraud
08 Accepted with identification
11 Approved VIP Client
12 Invalid transaction
13 Invalid amount
14 Card number does not exist
15 Issuer number or Bin does not exist
19 Retry the transaction
25 Record not in the file (not processed)
28 File temporarily unavailable
30 Message with format error
39 Nonexistent Credit Account
40 Request to unsupported function
41 Hold Card - The card is lost
43 Retain Card - The card is stolen
51 Insufficient funds
52 Non-Existent Current Account
53 Nonexistent Savings Box
54 The card is expired
55 The PIN is incorrect or has not been entered.
57 Unauthorized transaction
58 Transaction not allowed on this device
61 Cash Advance is exceeded
62 Restricted card is invalid in this region/Incorrect data
63 Security breach
65 Exceeds the maximum extraction frequency limit
75 Maximum PIN entry exceeded
76 Previous message not found
77 Invalid repeated message
78 The specified account does not exist
79 Transaction previously reversed
80 Invalid Date
81 Cryptographic Error in the Pin
84 Time limit exceeded
85 There is no reason to deny the transaction
86 PIN or the CVV cannot be verified
87 Finalized totals for this trading day
88 The Switch cannot provide totals now.
89 Cannot receive the financial position
91 The transmitter is not operating
92 The transaction cannot be routed
93 The transaction cannot be completed
94 Duplicate transmission detected
96 The system is not functioning correctly.
N0 Stand-In Error
C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 19
ISO 8583 Message

N3 Cash Advance Service not available


N4 Cash Advance Limit Reached
N7 Invalid CVV2/CVC2
P1 Invalid PVV
Q1 Card authentication failure
Z3 Offline Sender Rejection

FOR THE REVERSIONS 0420

Code Description of the Return code


00 Reversion accepted.
02 Generic reversion
03 Invalid format received
21 Reversion not applied
32 Partial reversal
19 Time-out
82 Unknown termination

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 20


ISO 8583 message

Annex III
a) Network International Identification Field 24
Network Identification Descripción
010 Authorization Center
020 Terminal Pos
030 Terminal ATM
040 Cash Registers/Bank Cashiers
050 E-Commerce/Authorization Orders
060 Telephone Banking
070 Exterior Switch

b) Forwarding Institution Id Code Field 33


Network Identification Descripción
200 Infonet
300 Bepsa
400 Unicentro
600 Bancard
601 Bancard Web
602 Bancard Others
700 Visa
800 MasterCard
900 Cyberia
901 Telecel
902 Connection
903 CitiBank
904 InterBank
905 Parnet
906 Personal

c) Type of transaction Field 48 Subfield 1


Código Categoría Transaction description
A Car and vehicle rental
C Cash Advance
F Copetines Restaurant
H Hotels, Motels
O Hospitalizations, Tuition Payments
R Sales in retail stores
T Phones or Orders Purchases
U Unique ???
X Airlines and other Transportation Services
Z Dispensed by Automated Teller Machines (ATM)

d) CVV Entry Method Field 48 Subfield 10


Code Meaning
0: The Merchant intentionally does not send the CVV.
1: The CVV is present
2: Illegible CVV
9: The user declares that the CVV is not present

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 21


ISO 8583 Message

e) Currency Code Field 49


Currency Code Description of the coin
600 Guarani
840 American dollars

f)Tipo de cuenta Field 54 Subfield 1


Tipo de cuenta Account type
00 Not specified
10 Savings Box
20 Current Account
30 Credit Card
40 Universal Account

g) Network Management Information Code Field 70


Code Function
001 Sign-on (by BIN)
002 Sign-off (by BIN)
161 Dynamic Key Exchange
200 User Pin Exchange
270 Echo Text

h) Lock Code Field 127 Subfield 1


Code Function
41 Card reported as stolen
43 Card reported as lost
90 Control message to see if the application is active

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page. 22


ISO 8583 message

Annex IV

Message Format

I. Financial Messages

MESSAGE 200
NRO. DESCRIPTION OF THE ISO TYPE FORMAT Size
ISO (Bytes)
MTI a 4
PRIMARY BITMAP a 8
SECONDARY BITMAP a 8
2 PAN a LLVAR (2+19) 21
3 PROCESSING CODE n 6
4 AMOUNT TRANSACTION n 12
5 AMOUNT SETTLEMENT n 12
6 AMOUNT CARDHOLDER BILLING n 12
7 TRANSMISSION DATE AND TIME n MMDDhhmmss 10
9 CONVERSION RATE, SETTLEMENT a 8
10 CONVERSION RATE CARDHOLDER BILLING a 8
11 SYSTEM TRACE AUDIT n 6
12 LOCAL TRANSACTION TIME n hhmmss 6
13 DATE EFFECTIVE, LOCAL TRANSACTION n MMDD 4
14 DATE, EXPIRATION n YYMM 4
15 DATE, SETTLEMENT n MMDD 4
16 DATE, CONVERSION n MMDD 4
18 MERCHANT TYPE n 4
19 ACQUIRING INSTITUTION COUNTRY CODE n 3
22 POS ENTRY MODE n 4
24 NETWORK INTERNATIONAL IDENTIFICATION n 3
25 POS CONDITION CODE n 4
26 PIN DATA LENGTH n 2
32 ACQUIRER INSTITUTION CODE a LLVAR (2+11) 13
33 FORWARDING INSTITUTION CODE a LLVAR (2+11) 13
35 TRACK 2 DATA a LLVAR (2+37) 39
37 RETRIEVAL REFERENCE NUMBER n 12
41 CARD ACCEPTOR TERMINAL ID a 8
42 CARD ACCEPTOR ID CODE n 15
43 CARD ACCEPTOR NAME a 40
44 ADDITIONAL RESPONSE DATA a LLVAR(2+99) 101
45 TRACK 1 a LLVAR (2+76) 78
48 ADDITIONAL DATA a LLLVAR(3+255) 258
49 CURRENCY CODE TRANSACTION n 3
50 CURRENCY CODE SETTLEMENT n 3
51 CURRENCY CODE CARDHOLDER BILLING n 3
52 PIN DATA a EMPAQ. HEXA 8
61 POS DATA(MST) FOR NATIONAL USE (ISO) a LLVAR (2+26) 28
102 ACCOUNT 1 a 28
103 ACCOUNT 2 a 28
Maximum possible length of the message (Bytes) 835

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 23


ISO 8583 Message

MENSAJE 210
NRO. DESCRIPTION OF THE ISO TYPE FORMAT Size
ISO Bytes
MTI a 4
0 PRIMARY BITMAP a 8
1 SECONDARY BITMAP a 8
2 PAN n LLVAR (2+19) 21
3 PROCESSING CODE n 6
4 AMOUNT TRANSACTION n 12
5 AMOUNT SETTLEMENT n 12
6 CARDHOLDER BILLING AMOUNT n 12
7 TRANSMISSION DATE AND TIME n MMDDhhmmss 10
9 CONVERSION RATE, SETTLEMENT a 8
10 CONVERSION RATE CARDHOLDER BILLING a 8
11 SYSTEM TRACE AUDIT n 6
12 LOCAL TIME TRANSACTION n hhmmss 6
13 DATE EFFECTIVE, LOCAL TRANSACTION n MMDD 4
14 DATE, EXPIRATION n YYMM 4
15 DATE, SETTLEMENT n MMDD 4
16 DATE, CONVERSION n MMDD 4
18 MERCHANT TYPE n 4
19 ACQUIRING INSTITUTION COUNTRY CODE n 3
22 POS ENTRY MODE n 4
24 NETWORK INTERNATIONAL IDENTIFIER n 3
26 PIN DATA LENGTH n 2
32 ACQUIRER INSTITUTION CODE n LLVAR (2+11) 13
33 FORWARDING INSTITUTION CODE n LLVAR (2+11) 13
35 TRACK 2 DATA a LLVAR (2+37) 39
37 RETRIEVAL REFERENCE NUMBER n 12
38 APPROVAL CODE a 6
39 ACTION CODE a 2
41 CARD ACCEPTOR TERMINAL ID a 8
42 CARD ACCEPTOR ID CODE n 15
43 CARD ACCEPTOR NAME a 40
44 ADDITIONAL RESPONSE DATA a LLVAR (2+99) 101
45 TRACK 1 a LLVAR (2+76) 78
47 ADDITIONAL DATA (Extracts - Payments) a LLLVAR (3+980) 983
48 ADDITIONAL DATA a LLLVAR(3+255) 258
49 CURRENCY CODE TRANSACTION n 3
50 CURRENCY CODE SETTLEMENT n 3
51 CURRENCY CODE CARDHOLDER BILLING n 3
52 PIN DATA a EMPAQ. HEXA 8
54 ADDITIONAL AMOUNTS a LLLVAR (3+108) 111
61 POS DATA(MST) FOR NATIONAL USE (ISO) a LLVAR (2+26) 28
102 ACCOUNT 1 n 28
103 ACCOUNT 2 n 28
126 VECTOR SELECTION ACCOUNT OAR a LLLVAR(3+280) 283
Maximum possible message length (Bytes) 2216

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 24


ISO 8583 Message

MENSAJE 420
NRO. DESCRIPTION OF THE ISO TYPE FORMAT Size
ISO (Bytes)
MTI a 4
PRIMARY BITMAP a 8
SECONDARY BITMAP a 8
2 PAN n LLVAR (2+19) 21
3 PROCESSING CODE n 6
4 AMOUNT TRANSACTION n 12
5 AMOUNT SETTLEMENT n 12
6 AMOUNT CARDHOLDER BILLING n 12
7 TRANSMISSION DATE AND TIME n MMDDhhmmss 10
9 CONVERSION RATE, SETTLEMENT a 8
10 CONVERSION RATE CARDHOLDER BILLING a 8
11 SYSTEM TRACE AUDIT n 6
12 TIME LOCAL TRANSACTION n hhmmss 6
13 DATE EFFECTIVE, LOCAL TRANSACTION n MMDD 4
14 DATE, EXPIRATION n YYMM 4
15 DATE, SETTLEMENT n MMDD 4
16 DATE, CONVERSION n MMDD 4
18 MERCHANT TYPE n 4
19 ACQUIRING INSTITUTION COUNTRY CODE n 3
22 POS ENTRY MODE n 4
24 NETWORK INTERNATIONAL IDENTIFIER n 3
32 ACQUIRER INSTITUTION CODE n LLVAR (2+11) 13
33 FORWARDING INSTITUTION CODE n LLVAR (2+11) 13
35 TRACK 2 DATA a LLVAR (2+37) 39
37 RETRIEVAL REFERENCE NUMBER n 12
38 APPROVAL CODE a 6
39 ACTION CODE a 2
41 CARD ACCEPTOR TERMINAL ID a 8
42 CARD ACCEPTOR ID CODE n 15
43 CARD ACCEPTOR NAME a 40
45 TRACK 1 a LLVAR (2+76) 78
48 ADDITIONAL DATA a LLLVAR(3+255) 258
49 CURRENCY CODE TRANSACTION n 3
50 CURRENCY CODE SETTLEMENT n 3
51 CURRENCY CODE CARDHOLDER BILLING n 3
61 POS DATA a LLVAR (2+26) 28
90 ORIGINAL DATA ELEMENTS a 42
95 REPLACEMENT AMOUNTS n 36
102 ACCOUNT 1 n 28
103 ACCOUNT 2 n 28
Maximum possible length of the message (Bytes) 806

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 25


ISO 8583 Message

MENSAJE 430
NRO. DESCRIPTION OF THE ISO TYPE FORMAT Size
ISO (Bytes)
MTI a 4
PRIMARY BITMAP a 8
SECONDARY BITMAP a 8
2 PAN n LLVAR (2+19) 21
3 PROCESSING CODE n 6
4 AMOUNT TRANSACTION n 12
5 AMOUNT SETTLEMENT n 12
6 AMOUNT CARDHOLDER BILLING n 12
7 TRANSMISSION DATE AND TIME n MMDDhhmmss 10
9 CONVERSION RATE, SETTLEMENT a 8
10 CONVERSION RATE CARDHOLDER BILLING a 8
11 SYSTEM TRACE AUDIT n 6
12 LOCAL TRANSACTION TIME n hhmmss 6
13 DATE EFFECTIVE, LOCAL TRANSACTION n MMDD 4
14 DATE, EXPIRATION n YYMM 4
15 DATE, SETTLEMENT n MMDD 4
16 DATE, CONVERSION n MMDD 4
18 MERCHANT TYPE n 4
19 ACQUIRING INSTITUTION COUNTRY CODE n 3
22 POS ENTRY MODE n 4
24 NETWORK INTERNATIONAL IDENTIFIER n 3
32 ACQUIRER INSTITUTION CODE n LLVAR (2+11) 13
33 FORWARDING INSTITUTION CODE n LLVAR (2+11) 13
35 TRACK 2 DATA a LLVAR (2+37) 39
37 RETRIEVAL REFERENCE NUMBER n 12
38 APPROVAL CODE a 6
39 ACTION CODE a 2
41 CARD ACCEPTOR TERMINAL ID a 8
42 CARD ACCEPTOR ID CODE a 15
43 CARD ACCEPTOR NAME a 40
45 TRACK 1 a LLVAR (2+76) 78
48 ADDITIONAL DATA a LLLVAR(3+255) 258
49 CURRENCY CODE TRANSACTION n 3
50 CURRENCY CODE SETTLEMENT n 3
51 CURRENCY CODE CARDHOLDER BILLING n 3
61 POS DATA a LLVAR (2+26) 28
90 ORIGINAL DATA ELEMENTS a 42
95 REPLACEMENT AMOUNTS n 36
102 ACCOUNT 1 n 28
103 ACCOUNT 2 n 28
Maximum possible message length (Bytes) 806

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 26


ISO 8583 message

II. Administrative Messages

MENSAJE 300
NRO. DESCRIPTION OF THE ISO TYPE FORMAT Size
ISO (Bytes)
MTI a 4
PRIMARY BITMAP a 8
SECONDARY BITMAP a 8
2 PAN n LLVAR (2+19) 21
7 TRANSMISSION DATE AND TIME n MMDDHHMMSS 10
11 SYSTEM TRACE AUDIT n 6
14 DATE, EXPIRATION n YYMM 4
18 MERCHANT TYPE n 4
22 POS ENTRY MODE n 4
24 NETWORK INTERNATIONAL IDENTIFICATION n 3
25 POS CONDITION CODE n 4
26 PIN DATA LENGTH n 2
32 ACQUIRER INSTITUTION CODE a LLVAR (2+11) 13
33 FORWARDING INSTITUTION CODE a LLVAR (2+11) 13
35 TRACK 2 DATA a LLVAR (2+37) 39
37 RETRIEVAL REFERENCE NUMBER n 12
41 CARD ACCEPTOR TERMINAL ID a 8
42 CARD ACCEPTOR ID CODE n 15
43 CARD ACCEPTOR NAME a 40
TRACK 1 a LLVAR (2+76) 78
48 ADDITIONAL DATA a LLLVAR(3+255) 258
52 PIN DATA a EMPAQ. HEXA 8
91 FILE UPDATE CODE n 1
102 ACCOUNT 1 n 28
103 ACCOUNT 2 n 28
127 PRIVATE DATA 122
Maximum possible message length (Bytes) 741

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 27


ISO 8583 Message

MESSAGE 310

NRO. DESCRIPTION OF THE ISO TYPE FORMAT Size


ISO (Bytes)
MTI a 4
PRIMARY BITMAP a 8
SECONDARY BITMAP a 8
2 PAN n LLVAR (2+19) 21
7 TRANSMISSION DATE AND TIME n MMDDHHMMSS 10
11 SYSTEM TRACE AUDIT n 6
14 DATE, EXPIRATION n YYMM 4
18 MERCHANT TYPE n 4
22 POS ENTRY MODE n 4
24 NETWORK INTERNATIONAL IDENTIFIER n 3
32 ACQUIRER INSTITUTION CODE a LLVAR (2+11) 13
33 FORWARDING INSTITUTION CODE a LLVAR (2+11) 13
35 TRACK 2 DATA a LLVAR (2+37) 39
37 RETRIEVAL REFERENCE NUMBER n 12
38 APPROVAL CODE a 6
39 ACTION CODE a 2
41 CARD ACCEPTOR TERMINAL ID a 8
42 CARD ACCEPTOR ID CODE n 15
43 CARD ACCEPTOR NAME a 40
44 ADDITIONAL RESPONSE DATA a LLVAR (2+99) 101
47 ADDITIONAL DATA (Extracts - Payments) a LLLVAR (3+980) 983
48 ADDITIONAL DATA a LLLVAR(3+255) 258
91 FILE UPDATE CODE n 1
102 ACCOUNT 1 n 28
103 ACCOUNT 2 n 28
127 PRIVATE DATA 122
Maximum possible message length (Bytes) 1819

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 28


ISO 8583 message

MESSAGE 302

NRO. DESCRIPTION OF THE ISO TYPE FORMAT Size


ISO Bytes
MTI a 4
PRIMARY BITMAP a 8
SECONDARY BITMAP a 8
2 PAN n LLVAR (2+19) 21
7 TRANSMISION DATE AND TIME n MMDDHHMMSS 10
11 SYSTEM TRACE AUDIT n 6
24 NETWORK INTERNATIONAL IDENTIFIER n 3
11 SYSTEM TRACE AUDIT n 6
33 FORWARDING INSTITUTION CODE n LLVAR (2+11) 13
44 ADDITIONAL RESPONSE DATA n LLVAR(2+99) 101
127 PRIVATE DATA 122
Maximum possible length of the message (Bytes) 296

MENSAJE 312

NRO. DESCRIPTION OF THE ISO TYPE FORMAT Size


ISO (Bytes)
MTI a 4
PRIMARY BITMAP a 8
SECONDARY BITMAP a 8
2 PAN n LLVAR (2+19) 21
7 TRANSMISSION DATE AND TIME n MMDDHHMMSS 10
11 SYSTEM TRACE AUDIT n 6
24 NETWORK INTERNATIONAL IDENTIFIER n 3
33 FORWARDING INSTITUTION CODE n LLVAR (2+11) 13
39 ACTION CODE a 3
44 ADDITIONAL RESPONSE DATA n LLVAR(2+99) 101
127 PRIVATE DATA 122
Maximum possible length of the message (Bytes) 299

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 29


ISO 8583 Message

III. Network/Key Management

MESSAGE 800

NRO. DESCRIPTION OF THE ISO TYPE FORMAT Size


ISO (Bytes)
MTI a 4
PRIMARY BITMAP a 8
SECONDARY BITMAP a 8
2 PAN (BIN) n LLVAR (2+19) 21
7 TRANSMISSION DATE AND TIME n MMDDhhmmss 10
11 SYSTEM TRACE AUDIT n 6
24 NETWORK INTERNATIONAL IDENTIFIER n 3
32 ACQUIRER INSTITUTION CODE a LLVAR (2+11) 13
33 FORWARDING INSTITUTION CODE n LLVAR (2+11) 13
44 ADDITIONAL RESPONSE DATA n LLVAR(2+99) 101
70 NETWORK MANAGEMENT INFORMATION CODE n 3
96 MESSAGE SECURITY CODE a 32
Maximum possible message length (Bytes) 213

MENSAJE 810

NRO. DESCRIPTION OF THE ISO TYPE FORMAT Size


ISO (Bytes)
MTI a 4
PRIMARY BITMAP a 8
SECONDARY BITMAP a 8
7 TRANSMISSION DATE AND TIME n MMDDhhmmss 10
11 SYSTEM TRACE AUDIT n 6
24 NETWORK INTERNATIONAL IDENTIFIER n 3
32 ACQUIRER INSTITUTION CODE a LLVAR (2+11) 13
33 FORWARDING INSTITUTION CODE n LLVAR (2+11) 13
39 ACTION CODE a 2
44 ADDITIONAL RESPONSE DATA n LLVAR(2+99) 101
70 NETWORK MANAGEMENT INFORMATION CODE n 3
Maximum possible message length (Bytes) 171

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 30


ISO 8583 Message

MESSAGE 802
NRO. DESCRIPTION OF THE ISO TYPE FORMAT Size
ISO Bytes
MTI a 4
PRIMARY BITMAP a 8
SECONDARY BITMAP a 8
2 PAN a LLVAR (2+19) 21
7 TRANSMISSION DATE AND TIME n MMDDhhmmss 10
11 SYSTEM TRACE AUDIT n 6
12 TIME LOCAL TRANSACTION n hhmmss 6
13 DATE EFFECTIVE, LOCAL TRANSACTION n MMDD 4
14 DATE, EXPIRATION n YYMM 4
22 POS ENTRY MODE n 4
24 NETWORK INTERNATIONAL IDENTIFICATION n 3
25 POS CONDITION CODE n 4
26 PIN DATA LENGTH n 2
32 ACQUIRER INSTITUTION CODE a LLVAR (2+11) 13
33 FORWARDING INSTITUTION CODE a LLVAR (2+11) 13
35 TRACK 2 DATA a LLVAR (2+37) 39
37 RETRIEVAL REFERENCE NUMBER n 12
41 CARD ACCEPTOR TERMINAL ID a 8
42 CARD ACCEPTOR ID CODE n 15
44 ADDITIONAL RESPONSE DATA a LLVAR(2+99) 101
45 TRACK 1 a LLVAR (2+76) 78
48 ADDITIONAL DATA a LLLVAR(3+255) 258
52 PIN DATA a EMPAQ. HEXA 8
61 POS DATA(MST) FOR NATIONAL USE (ISO) a LLVAR (2+26) 28
70 NETWORK MANAGEMENT INFORMATION CODE n 3
96 MESSAGE SECURITY CODE a 32
Maximum possible length of the message (Bytes) 692

MESSAGE 812
NRO. DESCRIPTION OF THE ISO TYPE FORMAT Size
ISO (Bytes)
MTI a 4
PRIMARY BITMAP a 8
Secondary Bitmap a 8
2 PAN a LLVAR (2+19) 21
7 TRANSMISSION DATE AND TIME n MMDDhhmmss 10
11 SYSTEM TRACE AUDIT n 6
12 TIME LOCAL TRANSACTION n hhmmss 6
13 DATE EFFECTIVE, LOCAL TRANSACTION n MMDD 4
14 DATE, EXPIRATION n YYMM 4
22 POS ENTRY MODE n 4
24 NETWORK INTERNATIONAL IDENTIFICATION n 3
32 ACQUIRER INSTITUTION CODE a LLVAR (2+11) 13
33 FORWARDING INSTITUTION CODE a LLVAR (2+11) 13
37 RETRIEVAL REFERENCE NUMBER n 12
38 APPROVAL CODE a 6
39 ACTION CODE a 2
41 CARD ACCEPTOR TERMINAL ID a 8
42 CARD ACCEPTOR ID CODE a 15
44 ADDITIONAL RESPONSE DATA a LLVAR(2+99) 101
48 ADDITIONAL DATA a LLLVAR(3+255) 258
70 NETWORK MANAGEMENT INFORMATION CODE n 3
Maximum possible length of the message (Bytes) 509

C:\Users\DEVELOPMENT\AppData\Roaming\Skype\My Skype Received Files\Manual [Link] Page 31

You might also like