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 19.1
edited by Kristian Lingsom
on 2017/10/16 12:53
on 2017/10/16 12:53
To version 20.1
edited by Kristian Lingsom
on 2017/10/16 12:55
on 2017/10/16 12:55
Change comment: There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -15,7 +15,7 @@ 15 15 The third party host(s) connect to PayEx loadbalanser 16 16 17 17 18 -== (% style="font-size:16px" %)Supported massage types(%%)==18 +== Supported massage types == 19 19 20 20 |Type|Source|Reference 21 21 |1100|3rd party|[[**A(% lang="EN-US" style="font-size:9pt; tab-stops:44.75pt" %)UTHORISATION REQUEST (%%)1100/1110**>>AUTHORISATION REQUEST 1100/1110]] ... ... @@ -38,7 +38,6 @@ 38 38 * (% style="tab-stops:21.15pt" %)Only the Financial transaction advice (1220), Reversal Advice (1420) use repeat messages. Repeats are to be sendt according to xxxxxxx rules 39 39 * (% style="tab-stops:21.15pt" %)Advices won’t be declined by PayEx unless for a technical reason.(%%)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 thirsd party and PayEx support must be initiated. 40 40 41 - 42 42 == Message layout == 43 43 44 44 This section covers message types and fields supported by PayEx