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.30
edited by Dani Alexander Berentzen
on 2017/11/07 12:27
on 2017/11/07 12:27
To version 30.31
edited by Pål-Eirik Askerød
on 2017/11/07 14:44
on 2017/11/07 14:44
Change comment: There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -xwiki:XWiki. dab1 +xwiki:XWiki.pea - Content
-
... ... @@ -28,8 +28,8 @@ 28 28 29 29 * Message types included in the table above are supported unless otherwise specified. E-g reconciliation is not currently supported. 30 30 Use links to different message types for details on specific messages. 31 -Only the Financial transaction advice (1220), Reversal Advice (1420) use repeat messages. Repeats are to be sent according to xxxxxxxrules32 -* 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.31 +Only the Financial transaction advice (1220), Reversal Advice (1420) use repeat messages(1221 and 1421). Repeats are to be sent according to rules below. 32 +* 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 with exponential wait period between retires. After 6 retry attempts have failed manual intervention by third party and PayEx support must be initiated. 33 33 34 34 == Message layout == 35 35 ... ... @@ -125,7 +125,7 @@ 125 125 126 126 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 merchant might not be reimbursed. 127 127 128 -== == 128 +== == 129 129 130 130 == PIN Validation == 131 131 ... ... @@ -152,10 +152,8 @@ 152 152 153 153 [[RESPONSE CODES>>doc:.Response codes.WebHome]] 154 154 155 -(% class="wikigeneratedid" %) 156 -== == 155 +== == 157 157 158 -(% class="wikigeneratedid" %) 159 159 == Message field overview == 160 160 161 161 **P-3 PROCESSING CODE**