Changes for page Payment Service Provider API ISO 8583:1993 (IFSF) H2H description
Last modified by Bjørnar Ruud on 2021/03/18 10:47
From version 26.1
edited by Kristian Lingsom
on 2017/10/16 15:10
on 2017/10/16 15:10
To version 27.1
edited by Kristian Lingsom
on 2017/10/16 15:33
on 2017/10/16 15:33
Change comment: There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -133,7 +133,6 @@ 133 133 * P-53 – Security related information 134 134 135 135 136 - 137 137 == Message field details == 138 138 139 139 ... ... @@ -183,7 +183,7 @@ 183 183 ))) 184 184 |Pos 5: Cardholder present|0: Cardholder present 185 185 |Pos 6: Card present|1: Card present 186 -|Pos 7: Card data input mode|2: Magnetic stripe read 185 +|Pos 7: Card data input mode|2: Magnetic stripe read 187 187 3: Bar code 188 188 5: ICC 189 189 6: Key entered A: RFID ... ... @@ -257,4 +257,94 @@ 257 257 258 258 **P-39 ACTION CODE** 259 259 260 -The following action codes are supported by OASE. Every action code not present in this table should be considered as declined. 259 +See action code page for codes that can be returned by PayEx. 260 + 261 + 262 +**P-41 Card acceptor terminal identification** 263 +Needs to be unique per POS terminal at the merchant site. For Inndoor terminals use the range 1-99 and for outdoor terminals 100-199. PayEx needs to be informed of how many terminals that are installed at the merchant site. 264 + 265 +**P-42 Card acceptor identification code** 266 + 267 +8 digit unique ID provided by PayEx for each merchant. 268 + 269 +**P-43 Card acceptor name/location** 270 + 271 +The name and location of the card acceptor. 272 + 273 +**P-48 MESSAGE CONTROL DATA ELEMENTS** 274 +Used for the control of messages between the POS and the FEP. These are present in field 48 as a variable content data element. It uses a standard bit map to identify the specific data elements present in field 48. The format is LLLVAR with a maximum length of 999. The 8 byte bit map is the first item (element 48-0) in the data element. 275 + 276 +P-48-4 BATCH/SEQUENCE NUMBER 277 + 278 +This field identifies the transactions associated with a particular settlement period. This number starts at one and increments with each Reconciliation. 279 + 280 +P-48-8 CUSTOMER DATA 281 + 282 +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 fuelling, 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 (\). (Note: the LVAR method is not used for these entries.) The entire data element has a maximum length of 250 bytes and is parsed as an LLLVAR field. 283 + 284 +|=Element|=Name|=Attribute|=Description 285 +|48-8-1|Number of customer data fields|n2|Count of customer data entries to follow.Note: this value must be from 1 to 16. 286 +|48-8-2|Type of customer data|an 1|Identifies the type of customer data entered. (see P48-8-2) 287 +|48-8-3|Value of customer data|ans...99|Data entered by customer orcashier. 288 + 289 + 290 +P-48-8-2 TYPE OF CUSTOMER DATA 291 + 292 +|=Code|=Description 293 +|1|Vehicle Number 294 +|3|Driver ID 295 +|4|Mileage 296 +|5|Driver license number 297 +|B|Unit number / Fleed ID 298 +|D|Customer verification code 299 +|G|Alphanumeric entred data 300 +| | 301 + 302 + 303 +**P-48-9 TRACK II OF VEHICLE CARD** 304 + 305 +The information encoded on track 2 of the magnetic stripe as defined in ISO7813, excluding beginning and ending sentinels and longitudinal redundancy check characters. 306 + 307 +**P-48-14 PIN ENCRYPTION METHODOLOGY** 308 + 309 +Fixed value ‘33’: ZKA MS/SK PAC H2H 310 +When P-52 is present, this field must also be present. When field P-52 is NOT present, field 48-14 should also NOT be present. 311 + 312 +The value supported by PayEx is ‘33’ and refers to 3DES ZKA UKPT. Other values are not supported. 313 + 314 +The first digit (3) refers to key management type ‘ZKA UKPT’ and the second digit (3) refers to the cryptographic algorithm ‘3DES with double length key’. A double length key means 2X56 bits effective key length. 315 + 316 + 317 +**P-48-32 VAT PERCENTAGES** 318 + 319 +List of VAT codes accompanied with their corresponding VAT percentage. 320 + 321 +The purpose of this field is to link the VAT codes as used in field P-63 Product data, P-63-8 tax code, to actual VAT percentages. As the incoming link can be multi-country, and PayEx does not have product codes per VAT rate, the VAT rates need to be provided in every transaction. 322 + 323 +Individual items are separated with a backslash character. 324 +Only VAT codes used in the product data (P-63) need to be described in this array. Others will be ignored. 325 + 326 + 327 +**P-48-37 VEHICLE IDENTIFICATION ENTRY MODE** 328 +Only present when a vehicle number is available (P48-8). Defines how the vehicle number was entered: 329 + 330 +0 - Manual entry 331 +1- On the Card 332 +2 - Automatic Licence Plate Recognition 333 + 334 +**P-48-38 PUMP LINKED INDICATOR** 335 + 336 +Indicating whether the fuel pump reading is is linked to the payment terminal: 337 +0 – Unspecified 338 +1 – Pump-linked 339 +2 – Pump not linked 340 + 341 + 342 +**P-48-39 DELIVERY NOTE NUMBER** 343 +Number allocated by the terminal given to the customer as printed on the ticket. 344 + 345 +**P-49 CURRENCY CODE , TRANSACTION** 346 +All transactions are in local currency, as defined during system installation. Actual value is as defined by ISO 4217. 347 + 348 +**P-52 PIN DATA** 349 +ISO 9564-1 format 0 PIN block encrypted with ZKA MK/SK PAC.