Last modified by Bjørnar Ruud on 2021/03/18 10:47
From version 30.13
edited by Pål-Eirik Askerød
on 2017/11/01 13:14
To version 30.14
edited by Pål-Eirik Askerød
on 2017/11/01 13:24
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -26,9 +26,9 @@
26 26  |1820/1830|[[NETWORK MANAGEMENT>>doc:.NETWORK MANAGEMENT 1820/1830.WebHome]]
27 27  |1520/1521/1530|RECONCILIATION REQUEST (**Currently not supported)**
28 28  
29 -* Message types not included in the table above are not supported. E-g reconciliation is not supported
29 +* Message types included in the table above are supported unless specified. E-g reconciliation is not currently supported.
30 30  Only the Financial transaction advice (1220), Reversal Advice (1420) use repeat messages. Repeats are to be sent according to xxxxxxx rules
31 -* Advice can be declined by PayEx for technical reasons. In this case the third party host need to retry the advice until manual intervention or the advice has been accepted. It’s expected that the third party implement a retry delay (to-be-defined). After 6 retry attemps have failed manual intervention by third party and PayEx support must be initiated.
31 +* Advice can be declined by PayEx for technical reasons. In this case the third party host need to retry the advice until manual intervention or the advice has been accepted. It’s expected that the third party implement a retry delay (to-be-defined). After 6 retry attempts have failed manual intervention by third party and PayEx support must be initiated.
32 32  
33 33  == Message layout ==
34 34  
... ... @@ -120,11 +120,10 @@
120 120  30323135
121 121  )))|15
122 122  
123 -The PayEx response timeout is set to XX seconds. If after xx+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)
123 +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)
124 124  
125 125  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.
126 126  
127 -(% class="wikigeneratedid" %)
128 128  == ==
129 129  
130 130  == PIN Validation ==
... ... @@ -137,9 +137,10 @@
137 137  * P-52 – PIN data
138 138  * P-53 – Security related information
139 139  
140 -(% class="wikigeneratedid" %)
141 -== ==
139 +(% class="wikigeneratedid" id="H-1" %)
140 +See security documentation for details.
142 142  
142 +
143 143  == Security documentation ==
144 144  
145 145  Here you can find details regarding the security aspects of this H2H integration.
... ... @@ -146,7 +146,6 @@
146 146  
147 147  __[[SECURITY SPECIFICATION>>doc:.PayEx IFSF H2H Security specification.WebHome]]__
148 148  
149 -== ==
150 150  
151 151  == Message field details ==
152 152  
... ... @@ -352,7 +352,6 @@
352 352  
353 353  See[[ security documentation>>doc:.PayEx IFSF H2H Security specification.WebHome]] section for details.
354 354  
355 -
356 356  
357 357  **P-56 ORIGINAL DATA ELEMENTS**
358 358  
... ... @@ -414,11 +414,13 @@
414 414  
415 415  **P-64 MAC**
416 416  
417 -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).
415 +MAC is calculated/verified according to the “ANS X9.9 Option 1 (binary data) procedure using ISO 16609 CBC-mode Triple-DES”.
418 418  
419 -The input for the MAC calculation/verification will be the SHA-256 of the IFSF message. The message length header and the MAC block itself are not included, however the MAC bit in the bitmap is part of the message and is already set when calculating the MAC.
417 +See [[security documentation>>doc:.PayEx IFSF H2H Security specification.WebHome]] for details.
420 420  
421 421  
422 422  **P-127 Encrypted data**
423 423  
424 424  This field contains the encrypted track2 data. See [[security documentation>>doc:.PayEx IFSF H2H Security specification.WebHome]] section for details on how to generate this field.
423 +
424 +