ISO 8583

ISO 8583 provides a framework for creating protocols for the exchange of financial transaction messages. Typically, these are messages that involve transactions originating from cards of some sort or the other, be they credit or debit cards. It's important to realize that 8583 itself is not a protocol, just as XML isn't a file format. XML can be considered a description of how to specify file formats for structured data according to a set of rules. ISO 8583 is a metaprotocol providing a set of rules for the definition of financial transaction protocols.

As such, a variety of ISO 8583 protocols exist, a famous example being Visa's BASE I protocol for transaction authorization. There's proprietary protocols POS terminals use to communicate with their hosts, and scores of other standards defined by equipment manufacturers, software vendors, banks or national standardization bodies. Chances are, if you swipe a plastic card through a machine, be it POS Terminal or ATM, the transaction will be transported by an 8583 family protocol somewhere en route to the bank. So remember, if a vendor promises you their product speaks ISO, make sure they speak the ISO 8583 flavor that you're looking for.

Back to the standard, unlike RFCs, ECMA standards, or a number of other standardization documents, the ISO 8583 standard is NOT freely available and there is no place on the Internet where it can be downloaded. This applies to most international standards published by ISO, by the way.

The standard can be purchased from ISO directly or in some cases from your country's standardization organization, e.g. ANSI in the US or DIN in Germany. Wherever you buy them, they'll end up costing around $150 for a PDF document.

The standard, officially titled "Financial transaction card originated messages -- Interchange message specifications" is comprised of three parts:

• Part 1: Messages, data elements and code values
• Part 2: Application and registration procedures for Institution Identification Codes (IIC)
• Part 3: Maintenance procedures for messages, data elements and code values

For implementation issues, Part 1 is most likely what you are looking for. Implementations based on older version of the standard from 1987 or 1993 are still widely in use, but to my knowledge, these versions are no longer available for sale by ISO. The currently available 2003 edition of the standard is sufficient for implementation purposes, though.

ISO 8583 :: Message Structure

ISO 8583 messages consist of 3 parts. The MTI (Message Type Indicator), the bitmap and finally the actual message data, grouped into a number of elements.

• The MTI is a four digit numeric code which, as the name suggests, contains information about the message type of the current message. This includes information about the ISO version, the message function and who's sending it.

• The MTI is followed by the bitmap which indicated which elements are present in the body of the message. In typical implementations, the bitmap is really a vector of single bits, either 8 or 16 bytes in length and thus can indicate the presence or absence or 64 or 128 data elements in the body of the message.

• The bitmap is followed by the a series of data elements or fields, some of which may be further subdivided into subfields. The specific mode of data encoding varies from field to field. ISO 8583 specifies the description and encoding information for a number of fields. Some of these definitions are more or less constant across all ISO 8583 implementations, for example the card number is nearly always contained in a field indicated by bit 2 and named "PAN". In general though, the meaning of the fields and their encoding is specific to the ISO 8583 dialect.

ISO 8583 :: MTI

As it's name suggests, the message type indicator provides information about the type of message we are dealing with. The MTI consists of four components describing version, class, function and originator of the message. Typically, the four MTI components are encoded as two bytes, with each half-byte or nibble representing one of the components. For example, a message beginning 0x01 0x00 has the version info set to 0, the class set to 1, and function and originator fields both set to 0.

Version

This is the first piece of information contained in the message, indicating the ISO standard version the message is based on. The following version values are defined:

Value	Version
0	1987
1	1993
2	2003
3-9	Reserved for ISO use

Message Class

the next position of the MTI provides information about the message class that the message is categorized as:

Value	Message Class
0	Reserved for ISO use
1	Authorization
2	Financial presentment
3	File action
4	Reversal/Chargeback
5	Reconciliation
6	Administrative
7	Fee collection
8	Network management
9	Reserved for ISO use

At this point, one could asked oneself naively, what exactly do these classes mean? How are 'Financial Presentment' and 'Financial Presentment' different? What about the difference between the 'Administrative' and 'Network management' classes? It turns out that those are very good questions and not everybody using 8583 to create a protocol came up with identical answers. A semantically identical message marked 'Authorization' in one protocol may be 'Financial Presentment' in another. So vaguely, the classes should mean roughly what you think they mean, but you need to check the description of the protocol you're talking about to be certain.

Message Function

The following table contains the possible values of the message function component of the MTI. Note that here again the precise meaning of these functions are dependent on the flavor of ISO you're using.

Value	Message Function
0	Request
1	Request response
2	Advice
3	Advice response
4	Notification
5	Notification acknowledgment
6	Instruction
7	Instruction acknowledgment
8,9	Reserved for ISO use

Again, don't ask what the difference is between an 'Advice', a 'Notification' and an 'Instruction'. The answer is: it depends.

Transaction Originator

The final component is information about who initiated the transaction. The possible values are:

Value	Message Function
0	Acquirer
1	Acquirer Repeat
2	Card Issuer
3	Card Issuer Repeat
4	Other Originator
5	Other Originator Repeat
6-9	Reserved for ISO

An important aspect to note is the existence of 'Repeat' messages. In case no response was received, it's usually possible to resend the identical message with the originator information set to 'Repeat'.

MTI example

A typical message a new terminal sends out when first connected might be an 0800 message. Looking up the information above, we see the terminals protocol is old'ish (1987). The message class is 'Network Management', the message's function is a 'Request' and it's being sent by the 'Acquirer'. You could argue about the sense of claiming the acquirer sent the message when in fact it's being sent by a terminal at the merchant.

If the host the terminal is trying to communicate with answers, it would send back a 08100801 message, indicating the message to be a repeat. message. The message type is identical, apart from being a 'response' and not a 'request'. But, if the terminal doesn't receive an answer from the host, the terminal may try to resend the message, this time as a

When the answer from the host finally arrives, the terminal will be able to tell apart delayed answers to the first (0810) message and answers to the repeat (0811).

Bitmaps

Within ISO 8583, a bitmap is a field or subfield within a message which indicates which other data elements or data element subfields may be present elsewhere in a message.

A message will contain at least one bitmap, called the Primary Bitmap which indicates which of Data Elements 1 to 64 are present. A secondary bitmap may also be present, generally as data element one and indicates which of data elements 65 to 128 are present. Similarly, a tertiary, or third, bitmap can be used to indicate the presence or absence of fields 129 to 192, although these data elements are rarely used.

The bitmap may be transmitted as 8 bytes of binary data, or as 16 hexadecimal characters 0-9, A-F in the ASCII or EBCDIC character sets.

A field is present when the specific bit in the bitmap is true, i.e. byte '82x is binary '1000 0010' which means fields 1 and 7 are present in the message

Data Elements

Data Elements are the individual fields carrying the transaction information. There are up to 128 data elements specified in the original ISO 8583:1987 standard, and up to 192 data elements in later releases. The 1993 revision added new definitions, deleted some, while leaving the message format itself unchanged.

While each data element has a specified meaning and format, the standard also includes some general purpose data elements and system- or country-specific data elements which vary enormously in use and form from implementation to implementation.

Each data element is described in a standard format which defines the permitted content of the field (numeric, binary, etc) and the field length (variable or fixed)**

Bit	Name	Format	Representation
1	Continuation bit		b8
2	Primary account number (PAN)	LLVAR	n..19
3	Processing code		an 6
(Constructed Element) 3-1 Transaction type code an 2 3-2 Account type code 1 an 2 3-3 Account type code 2 an 2
4	Amount transaction		n 16
(Constructed Element) 4-1 Currency code amount transaction n3 4-2 Currency minor unit amount transaction n1 4-3 Value amount transaction n 12
5	Amount reconciliation		n 16
(Constructed Element) 5-1 Currency code amount reconciliation n3 5-2 currency minor unit amount reconciliation n1 5-3 Value amount reconciliation n 12
6	Amount cardholder billing		n 16
(Constructed Element) 6-1 Currency code amount cardholder billing n3 6-2 Currency minor unit amount cardholder billing n1 6-3 Value amount cardholder billing n 12
7	Date and time transmission	MMDDhhmmss	n 10
8	Amount cardholder billing fee		n 12
(Constructed Element) 8-1 Currency code amount cardholder billing fee n3 8-2 Currency minor unit amount cardholder billing fee n1 8-3 Value amount cardholder billing fee n8
9	Conversion rate reconciliation		n8
10	Conversion rate cardholder billing		n8
11	Systems trace audit number		n 12
12	Date and time local transaction	CCYYMMDDhhmmss	n 14
(Constructed Element) 12-1 Date local transaction CCYYMMDD n8 12-2 Time local transaction hhmmss n6
13	Date effective	CCYYMM	n6
14	Date expiration	YYMM	n4
15	Date settlement	CCYYMMDD	n8
16	Date conversion	MMDD	n4
17	Date capture	MMDD	n4
18	Message error indicator	LLLVAR	ansb..140
(Constructed Element) 18-1 Error severity code n2 18-2 Message error code n4 18-3 Data element in error n3 18-4 Data sub-element in error n2 18-5 Dataset identifier in error b1 18-6 Dataset bit or Tag in error b2
19	Country code acquiring institution		n3
20	Country code primary account number (PAN)		n3
21	Transaction life cycle identification data		ans 22
(Constructed Element) 21-1 Life cycle support indicator ans 1 21-2 Life cycle trace identifier ans 15 21-3 Life cycle transaction sequence number n2 21-4 Life cycle authentication token n4
22	Point of service data code		b 12
(Constructed Element) 22-1 Card reading method used at POS b3 22-2 Cardholder verification method used at POS b3 22-3 POS environment b3 22-4 Security characteristics b3
23	Card sequence number		n3
24	Function code		n3
25	Message reason code		n4
26	Merchant category code		n4
27	Point of service capability		anb 25
(Constructed Element) 27-1 POS card reading capability b3 27-2 POS cardholder verification capability b3 27-3 Approval code length n1 27-4 Cardholder receipt data length n3 27-5 Card acceptor receipt data length n3 27-6 Cardholder display data length n3 27-7 Card acceptor display data length n3 27-8 ICC scripts data length n3 27-9 Magnetic Stripe Track 3 rewrite capability a1 27-10 Card capture capability a1 27-11 Pin input length capability b1
28	Date reconciliation	CCYYMMDD	n8
29	Reconciliation indicator		n3
30	Amounts original		n 32
(Constructed Element) 30-1 Original amount transaction n 16 30-1.1 Currency code original amount transaction n3 30-1.2 currency minor unit original amount transaction n1 30-1.3 Value original amount transaction n 12 30-2 Original amount reconciliation n 16 30-2.1 Currency code original amount reconciliation n3 30-2.2 Currency minor unit original amount reconciliation n1 30-2.3 Value original amount reconciliation n 12
31	Acquirer reference number		n 23
(Constructed Element) 31-1 User format identifier n1 31-2 Acquirer number n6 31-3 Julian processing date YDDD n4 31-4 Sequence number n 11 31-5 Luhn check digit n1
32	Acquiring institution identification code	LLVAR	n..11
33	Forwarding institution identification code	LLVAR	n..11
34	Electronic commerce data	LLLLVAR	b..9999
(Composite Element) 34-71 Account based digital signature LLVAR b..90 34-72 Authentication code Tag 80 ansb..50 34-72 Card acceptor certificate serial number LLVAR b..16 34-72 Cardholder certificate serial number LLVAR b..16 34-72 TransStain b 20 34-72 XID b 20
35	Track 2 data	LLVAR	z..37
36	Track 3 data	LLLVAR	z..104
37	Retrieval reference number		anp 12
38	Approval code		anp 6
39	Action code		n4
40	Service code		n3
41	Card acceptor terminal identification		ans 16
42	Card acceptor identification code	LLVAR	ans..35
43	Card acceptor name/location	LLLLVAR	ansb..9999
(Composite Element) 43-71 Card acceptor additional address information Tag 81 an..256 43-71 Card acceptor additional contact information LLVAR ans..30 43-71 Card acceptor city LLVAR ans..50 43-71 Card acceptor country code a3 43-71 Card acceptor customer service phone number ans 16 43-71 Card acceptor e-mail address LLVAR ans..99 43-71 Card acceptor internet URL LLLVAR ans..255 43-71 Card acceptor name LLVAR ans..50 43-71 Card acceptor phone number ans 16 43-71 Card acceptor postal code ans 10 43-71 Card acceptor state province or region code ans 3 43-71 Card acceptor street address LLVAR ans..99
44	Additional response data	LLLLVAR	ansb..9999
(Composite Element) 44-71 Card acceptor display data LLVAR ans. 99 44-71 Card acceptor receipt data LLVAR ans..99 44-71 Card issuer telephone number ans 16 44-71 Cardholder receipt data LLVAR ans..99 44-71 Cardholder display data LLVAR ans..99
45	Track 1 data	LLVAR	ans..76
46	Amounts fees	LLLVAR	ans..216
(Constructed Element) 46-1 Fee type code n2 46-2 Amount fee xn 13 46-2.1 Currency code amount fee n3 46-2.2 Currency minor unit amount fee n1 46-2.3 Value amount fee n8 46-3 Conversion rate fee n8 46-4 Amount reconciliation fee xn 13 46-4.1 Currency code amount reconciliation fee n3 46-4.2 Currency minor unit reconciliation fee n1 46-4.3 Value reconciliation fee n8
47	Additional data national	LLLVAR	ans..999
48	Additional data private	LLLVAR	ans..999
49	Verification data	LLLVAR	ans..999
(Composite Element) 49-71 Additional identification reference number LLVAR ans..30 49-71 Additional identification type n1 49-71 Card verification data n4 49-71 Cardholder billing address compressed ans 16 49-71 Cardholder billing postal code ans 10 49-71 Cardholder billing street address ans 40 49-72 Address verification result code an 1
50-51	Reserved for ISO
52	Personal identification number (PIN) data		b8
53	Security related control information	LLVAR	b..48
54	Amounts additional	LLLVAR	ans..126
(Constructed Element) 54-1 Account type additional amounts an 2 54-2 Amount type additional amounts an 2 54-3 Amount additional amounts xn 17 54-3.1 Currency code amount additional amounts n3 54-3.2 Currency minor unit amount additional amounts n1 54-3.3 Value amount additional amounts n 12
55	Integrated circuit card (ICC) system related data	LLLLVAR	b..9999
56	Original data elements	LLVAR	n..41
(Constructed Element) 56-1 Original message type identifier n4 56-2 Original system trace audit number n 12 56-3 Original date and time local transaction CCYYMMDDhhmmss n 14 56-4 Original acquiring institution identification code n..11
57	Authorisation life cycle code		n3
58	Authorising agent institution identification code	LLVAR	n..11
59	Transport data	LLLVAR	ans..999
60-61	Reserved for national use	LLLVAR	ans..999
62-63	Reserved for private use	LLLVAR	ans..999
64 or 128	Message authentication code (MAC) field		b4
65	Reserved for ISO use
66	Amounts original fees	LLLVAR	ans..216
(Constructed Element) 66-1 Original fee type code n2 66-2 Original amount fee xn 13 66-2.1 Currency code original amount fee n3 66-2.2 currency minor unit original amount fee n1 66-2.3 Value original amount fee n8 66-3 Original conversion rate fee n8 66-4 Original amount reconciliation fee. xn 13 66-4.1 Currency code original amount reconciliation fee n3 66-4.2 Currency minor unit original amount reconciliation fee n1 66-4.3 Value original amount reconciliation fee n8
67	Extended payment data		n2
68	Batch/file transfer message control		an 9
(Constructed Element) 68-1 Batch/file transfer acknowledgement code an 1 68-2 Batch/file transfer message sequence number n8
69	Batch/file transfer control data		ans 40
(Constructed Element) 69-1 Batch/file transfer message count n8 69-2 Batch/file transfer file identification ans 32
70	File transfer description data		n 18
(Constructed Element) 70-1 File transfer file size n6 70-2 File transfer elementary data record count n6 70-3 File transfer remaining elementary data record count n6
71	Reserved for ISO use
72	Data record	LLLLVAR	ansb..9999
73	Date action	CCYYMMDD	n8
74	Reconciliation data primary		n 156
(Constructed Element) 74-1 Credits amount n 16 74-2 Credits number n 10 74-3 Credits chargeback amount n 16 74-4 Credits chargeback number n 10 74-5 Credits reversal amount n 16 74-6 Credits reversal number n 10 74-7 Debits amount n 16 74-8 Debits number n 10 74-9 Debits chargeback amount n 16 74-10 Debits chargeback number n 10 74-11 Debits reversal amount n 16 74-12 Debits reversal number n 10
75	Reconciliation data secondary		n 90
(Constructed Element) 75-1 Authorisations number n 10 75-2 Authorisations reversal number n 10 75-3 Inquiries reversal number n 10 75-4 Inquiries number n 10 75-5 Fee collections number n 10 75-6 Payments number n 10 75-7 Payments reversal number n 10 75-8 Transfer number n 10 75-9 Transfer reversal number n 10
76-92	Reserved for ISO use
93	Transaction destination institution identification code	LLVAR	n..11
94	Transaction originator institution identification code	LLVAR	n..11
95	Card card issuer reference data	LLVAR	ans..99
96	Key management data	LLLVAR	b..999
97	Amount net reconciliation		xn 21
(Constructed Element) 97-1 Currency code Amount net reconciliation n3 97-2 Currency minor unit amount net reconciliation n1 97-3 Value amount net reconciliation xn 17
98	Payee		ans 25
99	Settlement institution identification code	LLVAR	an..11
100	Receiving institution identification code	LLVAR	n..11
101	File name	LLVAR	ans..99
102	Account identification 1	LLVAR	ans..28
103	Account identification 2	LLVAR	ans..28
104	Transaction specific data	LLLLVAR	ansb..9999
(Composite Element) 104-71 Free-form description data LLLVAR ans..999 104-72 Invoice alternate tax identifier ans 15 104-72 Invoice amount alternate tax n 12 104-72 Invoice amount alternate tax indicator Y = yes N = no space = unknown as 1 104-72 Invoice amount bottom line discount n 12 104-72 Invoice amount duty n 12 104-72 Invoice amount freight excluding tax n 12 104-72 Invoice amount freight including tax n 12 104-72 Invoice amount total tax n 12 104-72 Invoice card acceptor customer reference number LLVAR an..17 104-72 Invoice card acceptor invoice reference number LLVAR an..12 104-72 Invoice card acceptor order number LLVAR an..15 104-72 Invoice card acceptor tax reference number LLVAR an..20 104-72 Invoice card acceptor type ans 4 104-72 Invoice cardholder order reference number LLVAR an..22 104-72 Invoice cardholder's tax reference number LLVAR an..13 104-72 Invoice cost centre LLVAR a..20 104-72 Invoice customer reference. LLVAR ans..20 104-72 Invoice destination country code an 3 104-72 Invoice destination postal code LLVAR an..10 104-72 Invoice destination state/province code ans 3 104-72 Invoice freight tax rate n4 104-72 Invoice order date CCYYMMDD n8 104-72 Invoice original invoice number LLVAR an..15 104-72 Invoice ship from postal code LLVAR an..10 104-72 Invoice tax indicator 0 = Tax not included 1 = Tax included n1 104-72 Invoice value excluding tax n 12 104-73 Line item amount discount n 12 104-73 Line item amount tax n 12 104-73 Line item commodity code LLVAR an..16 104-73 Line item dataset sequence number b2 104-73 Line item descriptor LLVAR an..40 104-73 Line item discount indicator Y = yes N = no space = unknown as 1 104-73 Line item discount rate ans 5 104-73 Line item product code LLVAR an..15 104-73 Line item product quantity LLVAR n..12 104-73 Line item quantity minor unit n1 104-73 Line item tax rate n5 104-73 Line item tax type ans 4 104-73 Line item unit of measure LLVAR a..12 104-73 Line item unit price excluding tax LLVAR n..12 104-73 Line item value debit/credit indicator D=debit C=credit space = unknown as 1 104-73 Line item value excluding tax n 12 104-73 Line item value including tax n 12 104-74 Airline amount total fare n 12 104-74 Airline amount total fees n 12 104-74 Airline amount total taxes n 12 104-74 Airline carrier name LLVAR an..19 104-74 Airline customer reference. LLVAR ans..20 104-74 Airline date ticket issue CCYYMMDD n8 104-74 Airline invoice number an 6 104-74 Airline original currency code n3 104-74 Airline original invoice amount n 12 104-74 Airline passenger name LLVAR ans.. 104-74 Airline plan number an 2 104-74 Airline ticket agency name LLVAR an..2 104-74 Airline ticket issue address LLVAR ans.. 104-74 Airline ticket number LLVAR an..1 104-74 Airline travel agency code LVAR an 8 104-75 Trip leg amount departure tax n 12 104-75 Trip leg amount fare n 12 104-75 Trip leg amount fees n 12 104-75 Trip leg amount taxes n 12 104-75 Trip leg arrival time n4 104-75 Trip leg arrival time segment code A = a.m. P = p.m. space = unknown as 1 104-75 Trip leg carrier code an 2 104-75 Trip leg class of travel an 2 104-75 Trip leg conjunction ticket number LLVAR an..1 104-75 Trip leg coupon number ans 1 104-75 Trip leg dataset sequence number b2 104-75 Trip leg date of travel CCYYMMDD n8 104-75 Trip leg departure airport an 5 104-75 Trip leg departure time n4 104-75 Trip leg departure time segment code A = a.m. P = p.m. space = unknown as 1 104-75 Trip leg destination code an 5 104-75 Trip leg endorsements/restrictions LLVAR ans.. 104-75 Trip leg exchange ticket number LLVAR an..1 104-75 Trip leg fare basis code LLVAR an..1 104-75 Trip leg flight number ans 5 104-75 Trip leg number n2 104-75 Trip leg stop over code an 1 104-76 Auto amount adjusted n 12 104-76 Auto amount adjusted indicator code as 1 104-76 Auto amount vehicle insurance n 12 104-76 Auto customer service toll-free phone number ans 1 104-76 Auto distance unit of measure K = Kilometres M= Miles a1 104-76 Auto maximum free miles/kilometres n4 104-76 Auto odometer reading n8 104-76 Auto program code ans 2 104-76 Auto rental address LLVAR ans..26 104-76 Auto rental agreement reference LLVAR ans..25 104-76 Auto rental city LLVAR ans..18 104-76 Auto rental class identifier ans 4 104-76 Auto rental country ans 3 104-76 Auto rental date CCYYMMDD n8 104-76 Auto rental distance n5 104-76 Auto rental location identifier ans 10 104-76 Auto rental rate n 12 104-76 Auto rental rate time period D = daily W = weekly M = monthly space = unknown as 1 104-76 Auto rental state/province ans 3 104-76 Auto rental time HHMM n4 104-76 Auto renter name LLVAR ans..29 104-76 Auto return address LLVAR ans..26 104-76 Auto return city LLVAR ans..18 104-76 Auto return country ans 3 104-76 Auto return date CCYYMMDD n8 104-76 Auto return location identifier ans 10 104-76 Auto return state/province ans 3 104-76 Auto return time HHMM n4 104-76 Auto vehicle insurance indicator Y = yes N = no space = unknown as 1 104-76 Auto vehicle registration number an 17 104-77 Lodging amount bar/mini-bar n 12 104-77 Lodging amount billing adjustment n 12 104-77 Lodging amount gift shop n 12 104-77 Lodging amount laundry/dry cleaning n 12 104-77 Lodging amount other services n 12 104-77 Lodging amount other services indicator ans 3 104-77 Lodging amount phone charges n 12 104-77 Lodging amount restaurant/room service n 12 104-77 Lodging amount room rate n 12 104-77 Lodging amount room tax n 12 104-77 Lodging customer service toll-free phone number ans 16 104-77 Lodging date arrival CCYYMMDD n8 104-77 Lodging date departure CCYYMMDD n8 104-77 Lodging facility phone number ans 16 104-77 Lodging folio number ans 10 104-77 Lodging program code ans 2 104-78 Fleet amount bottom line discount n 12 104-78 Fleet amount total tax n 12 104-78 Fleet driver number/other identification number LLVAR n..17 104-78 Fleet line item value excluding tax n 12 104-78 Fleet line item value including tax n 12 104-78 Fleet motor fuel oil company brand name n4 104-78 Fleet motor fuel prompt code n1 104-78 Fleet motor fuel service type code ans 1 104-78 Fleet odometer reading n8 104-78 Fleet product code LLVAR an..15 104-78 Fleet product quantity LLVAR n..12 104-78 Fleet quantity minor unit n1 104-78 Fleet unit of measure LLVAR ans..12 104-78 Fleet unit price excluding tax n 12 104-78 Fleet unit price including tax n 12 104-78 Fleet vehicle registration number an 17
105-108	Reserved for ISO use
109	Reconciliation fee amounts credit	LLLVAR	ans..144
(Constructed Element) 109-1 Fee type code n2 109-2 Amount fee total n 12 109-3 Number fee total n 10
110	Reconciliation fee amounts debit	LLLVAR	ans..144
(Constructed Element) 110-1 Fee type code n2 110-2 Amount fee total n 12 110-3 Number fee total n 10
111-115	Reserved for private use
116-122	Reserved for national use	LLLVAR	ANS..999
123-127	Reserved for private use	LLLVAR	ANS..999
128 or 64	Message authentication code (MAC) field		b4