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 30.18

edited by Pål-Eirik Askerød
on 2017/11/02 14:46

To version 30.19

edited by Pål-Eirik Askerød
on 2017/11/03 13:46

Change comment: There is no comment for this version

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -2,7
          +2,7 @@
  (((
  = Overview =
--The purpose of the H2H PayEx link is to enable authorization and settlement of card transactions, where PayEx is end host for that card, or just an PSP. The third party host acts as a gateway in between payment terminals and PayEx.
++The purpose of the H2H PayEx link is to enable authorization and capture of card transactions, where PayEx is end host for that card, or just an PSP. The third party host acts as a gateway in between payment terminals and PayEx.
  [[image:pos server.png]]
@@ -121,9
          +121,9 @@
  30323135
  )))|15
--The PayEx response timeout is set to 30 seconds. If after 30+1 seconds, no response has been received, the third party host needs to take the appropriate action based on the message type. (E.g. send a reversal)
++The PayEx response timeout is set to 35 seconds. If after 35+1 seconds, no response has been received, the third party host needs to take the appropriate action based on the message type. (E.g. send a reversal)
--The third party host has the possibility to perform offline stand-in, thought this needs to be agreed with the indididual card issuers. Otherwise the station might not be reimbursed.
++The third party host has the possibility to perform offline stand-in, thought this needs to be agreed with the individual card issuers. Otherwise the station might not be reimbursed.
  ==   ==
@@ -178,37
          +178,6 @@
  A series of codes intended to identify terminal capability, terminal environment and presentation security data.
--|=Point of service date code|=Description
--|POS 1: Card data input capabilities|2: magnetic stripe read A: RFID
--B: Magnetic stripe reader and key entry
--C: Magnetic stripe reader, ICC and key entry
--D: Magnetic stripe reader and ICC
--|Pos 2: Cardholder authentication capability|1: PIN
--Y: Signature,plaintext/enciphered PIN offline and ‘no cvm’ capable, enciphered pin online
--|Pos 3: Card capture capability|0:None
--T: None and SDA/DDA/CDA capable
--|Pos 4: Operating environment|(((
--1: On premises of card acceptor, attended
--2: On premises of card acceptor, unattended
--)))
--|Pos 5: Cardholder present|0: Cardholder present
--|Pos 6: Card present|1: Card present
--|Pos 7: Card data input mode|2: Magnetic stripe read
--3: Bar code
--5: ICC
--6: Key entered A: RFID
--D:  Magnetic stripe read following failed chip card read
--|Pos 8: Cardholder authentication method|0: Not authenticated
--1: PIN
--5: Manual signature verification
--|Pos 9: Cardholder authentication entity|0: Not authenticated
--1: ICC
--2: Card acceptor device 3: Authorizing Agent
--|Pos 10: Card data output capability|1: None
--3: ICC
--|Pos 11: Terminal output capability|2: Printing
--4: Printing and display
--|Pos 12: PIN capture capability|C: Twelve characters
  **P-24 FUNCTION CODE**
@@ -223,7
          +223,7 @@
  **P-25 MESSAGE REASON CODE**
  |=reason code |=Description
--|1003|Card issuer unabailable
++|1003|Card issuer unavailable
  |1004|Terminal processed
  |1508|On-line forced by terminal
  |4000|Customer cancellation
@@ -288,41
          +288,27 @@
  **P-48-8-2 TYPE OF CUSTOMER DATA**
--1 - Vehicle Number
++1 - Vehicle ID
 - Driver ID
 - Mileage
--5 - Driver license number
--B - Unit number/fleet ID
--D - Customer verification code
--G - Alphanumeric entered data
++
--The information encoded on track 2 of the magnetic stripe as defined in ISO7813, excluding beginning and ending sentinels and longitudinal redundancy check characters.
--
--
  **P-48-9 TRACK II OF VEHICLE CARD**
++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.
++
  **P-48-14 PIN ENCRYPTION METHODOLOGY**
  See [[security documentation>>doc:.PayEx IFSF H2H Security specification.WebHome]] section for details.
--**P-48-32 VAT PERCENTAGES**
--
--List of VAT codes accompanied with their corresponding VAT percentage.
--
--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.
--
--Individual items are separated with a backslash character.
--Only VAT codes used in the product data (P-63) need to be described in this array. Others will be ignored.
--
--
  **P-48-37 VEHICLE IDENTIFICATION ENTRY MODE**
  Only present when a vehicle number is available (P48-8). Defines how the vehicle number was entered:
 - Manual entry
 - On the Card
--2 - Automatic Licence Plate Recognition
++2 - Automatic License Plate Recognition
  **P-48-38 PUMP LINKED INDICATOR**
@@ -342,7
          +342,6 @@
  **P-52 PIN DATA**
--ISO 9564-1 format 0 PIN block encrypted with PIN encryption key.
  See[[ security documentation>>doc:.PayEx IFSF H2H Security specification.WebHome]] section for details.
@@ -355,8
          +355,8 @@
  **P-56 ORIGINAL DATA ELEMENTS**
  Data elements of original transaction which contains the original “message identifier”, original “STAN” and original “date and time – local transaction”. This must be present if the message is preceded by an 1100 Authorisation Request, it can be omitted if the message is as a result of a store and forward transaction.
--In Payment advice : Link to previous Authorisation dialog
--In reversal advice    : Link to previous Authorisation request or previous Payment request being reversed.
++In Payment advice : Link to previous Authorization dialog
++In reversal advice   : Link to previous Authorization request or previous Payment request being reversed.
  **P-62 PRODUCT SETS AND MESSAGE DATA**
@@ -376,7
          +376,7 @@
  This data element provides the detailed information on the products purchased or selected by the customer. The first two fields (63-1, 63-2) appear once per transaction.  The next seven fields can be repeated up to 18 times.
--Each product is represented by seven fields: Product Code, Unit of Measure, Quantity, Unit Price, Amount, Taxcode and Additional product code. The variable length fields and the succeeding entry are separated by a back-slash (\).
++Each product is represented by seven fields: Product Code, Unit of Measure, Quantity, Unit Price, Amount, Tax code and Additional product code. The variable length fields and the succeeding entry are separated by a back-slash (\).
  Unit price and amount may be negative or positive, but the sum of the amounts in the product data must equal the transaction amount.
  The values of Quantity and Unit price may have a value that includes both integer and fractional values. The format of these fields consists of a single digit, which specifies the number of fractional digits following the integer, followed by the numeric value.
  The value must be numeric. The number of fractional digits has a maximum of 4. The Amount field may have fractional digits. The number of fractional digits is specified by the currency code.
@@ -412,8
          +412,6 @@
  **P-64 MAC**
--MAC is calculated/verified according to the “ANS X9.9 Option 1 (binary data) procedure using ISO 16609 CBC-mode Triple-DES”.
--
  See [[security documentation>>doc:.PayEx IFSF H2H Security specification.WebHome]] for details.
@@ -424,8
          +424,6 @@
  **P-128 MAC**
--MAC is calculated/verified according to the “ANS X9.9 Option 1 (binary data) procedure using ISO 16609 CBC-mode Triple-DES”.
++**This field is used for MAC if P-127 is present**. See [[security documentation>>doc:.PayEx IFSF H2H Security specification.WebHome]] for details.
--This field is used for MAC if P-127 is present. See [[security documentation>>doc:.PayEx IFSF H2H Security specification.WebHome]] for details.
--