Version 9.1 by Bjørnar Ruud on 2021/03/18 14:12
Show last authors
1 === **AUTHORIZATION REQUEST 1100** ===
2
3 |**Element number**|**Data element name**|**Presence**|**Format**|**Type**|**Size**|**Usage notes**
4 |3|Processing Code|M| |n|6|Fixed 000000. Other processing code values are currently not supported.
5 |4|Amount, transaction|M| |n|12|E.g.: 1 kr (NOK) value="000000000100"
6 |7|Date and time, transmission|M|(((
7 MMDDhhmmss
8 )))|n|10|E.g.: 1025123020
9 |11|Systems trace audit number|M| |n|6|Assigned by third party host. Unique pr request
10 |12|Date and time, local transaction|M|(((
11 YYMMDDhhmmss
12 )))|n|12|E.g.: 171025100515
13 |22|Point of service data code|M| |an|12|See [[table below>>doc:Main.POS.Payment Service provider API ISO8583_2 ( IFSF) H2H description.AUTHORISATION REQUEST 1100/1110||anchor="HP-22POINTOFSERVICEDATACODE"]] for details on this field and sub-fields.
14 |24|Function code|M| |n|3|(((
15 Fixed 101: Original Authorization. Other values are currently not supported.
16 )))
17 |25|Message reason code|M| |n|4|Fixed 1508. Online only
18 |26|Card acceptor business code|M| |n|4|5541 for indoor and 5542 for outdoor
19 |33|Forwarding Institution identification code|M|LL|n|..11|Unique id provided by PayEx used for all transactions from given 3rd party
20 |41|Card acceptor terminal identification|M| |n|8|Needs to be unique per POS terminal at the merchant site.
21 |42|Card acceptor identification code|M| |n|15|8 digit unique ID provided by PayEx for each merchant.
22 |48|Message control data elements|M|LLL|ans|..999|
23 |48-0|Bit map|M| |b|8|
24 |48-4|Batch/sequence number|M| |n|10|Assigned by third party host
25 |48-8|Customer data|C|LLL|ans|..250|See [[table below >>doc:Main.POS.Payment Service provider API ISO8583_2 ( IFSF) H2H description.AUTHORISATION REQUEST 1100/1110||anchor="HP-48-8Customerdata"]]for details on this field and sub-fields.
26 |48-9|Track II of vehicle card|O|LL|ns|..37|(((
27 Used to specify the second card in a transaction if a special card is needed in addition to the payment card to link a transaction to a loyalty account.
28 )))
29 |48-14|PIN Encryption Methodology|C| |ans|2|Present if online PIN. See [[security documentation>>doc:Main.POS.Payment Service provider API ISO8583_2 ( IFSF) H2H description.PayEx IFSF H2H Security specification.WebHome]] section for details.
30 |49|Currency code, transaction|M| |an|3|(((
31 Numeric currency code (ISO-4217 standard). E.g. "578" for NOK
32 )))
33 |52|PIN Data|C| |b|8|Present if online PIN. See [[security documentation>>doc:Main.POS.Payment Service provider API ISO8583_2 ( IFSF) H2H description.PayEx IFSF H2H Security specification.WebHome]] section for details.
34 |53|Security Related Control Information|M|LL|b|..48|See [[security documentation>>doc:Main.POS.Payment Service provider API ISO8583_2 ( IFSF) H2H description.PayEx IFSF H2H Security specification.WebHome]] section for details.
35 |61|Message text|O|LLL|ans|..894|
36 |127|PIN KSN|M|LLL|b|..999|See [[security documentation>>doc:Main.POS.Payment Service provider API ISO8583_2 ( IFSF) H2H description.PayEx IFSF H2H Security specification.WebHome]] section for details.
37 |128|MAC|M| |b|8|MAC field used when field 127 present. See [[security documentation>>doc:Main.POS.Payment Service provider API ISO8583_2 ( IFSF) H2H description.PayEx IFSF H2H Security specification.WebHome]] section for details.
38
39 === **AUTHORIZATION RESPONSE 1110** ===
40
41 |**Element number**|**Data element name**|**Presence**|**Format**|**Type**|**Size**|**Usage notes**
42 |3|Processing Code|ME| |n|6|
43 |4|Amount, transaction|M| |n|12|Authorized amount. The amount available to customer
44 |7|Date and time, transmission|M|(((
45 MMDDhhmmss
46 )))|n|10|E.g.: 1022150534
47 |11|Systems trace audit number|ME| |n|6|
48 |12|Date and time, local transaction|ME|(((
49 YYMMDDhhmmss
50 )))|n|12|E.g.: 171025100515
51 |30|Original amount|C| |n|24|Original amount if partial approval or decline.
52 |32|(((
53 Acquiring institution identification
54
55 code
56 )))|ME|LL|n|..11|
57 |38|Approval code|C| |ans|6|If transaction has been approved.
58 |39|Action code|M| |n|3|Action code. See [[action code section>>doc:Main.POS.Payment Service provider API ISO8583_2 ( IFSF) H2H description.Response codes.WebHome]] for available codes.
59 |41|Card acceptor terminal identification|ME| |n|8|
60 |42|Card acceptor identification code|ME| |n|15|
61 |48|Message control data elements|M|LLL|ans|..999|
62 |48-0|Bit map|M| |b|8|
63 |48-4|Batch/sequence number|ME| |n|10|
64 |49|Currency code, transaction|ME| |an|3|
65 |53|Security Related Control Information|M|LL|b|..48|See [[security documentation>>url:https://wiki.payex.com/xwiki/bin/view/Team%20Area/POS/Server/Documentation/POS/Payment%20Service%20provider%20API%20ISO8583_2%20%28%20IFSF%29%20H2H%20description/PayEx%20IFSF%20H2H%20Security%20specification/]] section for details.
66 |62|Product sets|C|LLL|ans|..999|
67 |62-1|Allowed product sets|C|LL|ans|..99|(((
68 This data element provides the information on the product sets that the customer is permitted to select. Each product set is represented by 3 bytes, sent to POS.
69 In an 1110 response they indicate the product sets the customer can purchase, before the purchase.
70 )))
71 |62-2|Device type|O| |n|1|
72 |62-3|Message text|O|LLL|ans|..894|
73 |64|MAC|M| |b|8|See [[security documentation>>url:https://wiki.payex.com/xwiki/bin/view/Team%20Area/POS/Server/Documentation/POS/Payment%20Service%20provider%20API%20ISO8583_2%20%28%20IFSF%29%20H2H%20description/PayEx%20IFSF%20H2H%20Security%20specification/]] section for details.
74
75 ==== ====
76
77 ==== **P-48-8 Customer data ** ====
78
79 The customer data is any data entered by the customer or cashier as required by the authorizer to complete the transaction. Transactions requiring customer data may be related to fleet fueling, cheque authorizations or any other type of retail store management functions. Up to sixteen separate entries are supported. Each entry consists of two elements, the type of customer data entered and the variable length value of the entered data. Successive entries are separated by a back-slash (\). The entire data element has a maximum length of 250 bytes and is parsed as an LLLVAR field. Currently supported sub-fields are listed below.
80
81 |**Element number**|**Data element name**|**Presence**|**Format**|**Type**|**Size**|**Usage notes**
82 |1|(((
83 VEHICLE ID
84 )))|O| |an|..10|
85 |3|(((
86 DRIVER ID
87 )))|O| |an|..8|(((
88
89 )))
90 |4|(((
91 ODOMETER READING
92 )))|O| |n|..8|(((
93 Odometer reading in kilometers.
94 )))
95
96 Example P-48-8:
97
98 "025 03 1 654321 \ 3 123456 \ 4 5000000"
99
100
101 ==== **P-22 POINT OF SERVICE DATA CODE** ====
102
103 |**Element number**|**Data element name**|**Presence**|**Format**|**Type**|**Size**|**Usage notes**
104 |1|(((
105 Pos 1: Card data input capabilities
106 )))|M| |an|1|(((
107 2: magnetic stripe read
108
109 5: ICC
110
111 A: RFID
112 B: Magnetic stripe reader and key entry
113 C: Magnetic stripe reader, ICC and key entry
114 D: Magnetic stripe reader and ICC
115 )))
116 |2|(((
117 Pos 2: Cardholder authentication capability
118 )))|M| |an|1|(((
119 1: PIN
120 Y: Signature, plaintext/enciphered PIN offline and ‘no cvm’ capable, enciphered pin online
121 )))
122 |3|Pos 3: Card capture capability|M| | | |0:None
123 T: None and SDA/DDA/CDA capable
124 |4|(((
125 Pos 4: Operating environment
126 )))|M| |an|1|(((
127 1: On premises of card acceptor, attended
128 2: On premises of card acceptor, unattended
129 )))
130 |5|Pos 5: Cardholder present|M| |an|1|0: Cardholder present
131 |6|Pos 6: Card present|M| |an|1|1: Card present
132 |7|Pos 7: Card data input mode|M| |an|1|(((
133 2: Magnetic stripe read
134 3: Bar code
135 5: ICC
136 6: Key entered
137
138 A: RFID
139
140 C: ICC data captured and passed unaltered
141 D: Magnetic stripe read following failed chip card read
142 )))
143 |8|Pos 8: Cardholder authentication method|M| |an|1|0: Not authenticated
144 1: PIN
145 5: Manual signature verification
146 |9|Pos 9: Cardholder authentication entity|M| |an|1|(((
147 0: Not authenticated
148
149 1: ICC
150
151 2: Card acceptor device
152
153 3: Authorizing Agent
154 )))
155 |10|Pos 10: Card data output capability|M| |an|1|1: None
156 3: ICC
157 |11|Pos 11: Terminal output capability|M| |an|1|2: Printing
158 4: Printing and display
159 |12|Pos 12: PIN capture capability|M| |an|1|(((
160 4: Four characters
161
162 C: Twelve characters
163 )))
164
165