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 24.3
edited by Kristian Lingsom
on 2017/10/16 13:55
on 2017/10/16 13:55
To version 25.1
edited by Kristian Lingsom
on 2017/10/16 14:28
on 2017/10/16 14:28
Change comment: There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -117,10 +117,19 @@ 117 117 |24 - Function code|n|ASCII|383331|831 118 118 |32 - Acquiring institution identification code|n|ASCII|TODO eksempel|TODO eksempel 119 119 120 - 121 121 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) 122 122 123 123 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. 124 124 125 125 125 +== PIN Validation == 126 + 127 +PayEx perform online PIN validation on paye,ent cards where PayEx is the acquirer, on all other cartds PIN is validated by the third party acuirer. PayEx will not interpret P-22 Point-Of-Service code to determine if it needs to validate PIN or not on PayEx fuel cards, but 3rd patry aquirers might so it's good practice to use P-22 correctly. 128 + 129 +Fields required for PIN validation are: 130 + 131 +* P-48-14 – PIN encryption Methodology 132 +* P-52 – PIN data 133 +* P-53 – Security related information 134 + 126 126