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 18.1
edited by Kristian Lingsom
on 2017/10/16 12:42
on 2017/10/16 12:42
To version 19.1
edited by Kristian Lingsom
on 2017/10/16 12:53
on 2017/10/16 12:53
Change comment: There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,10 +1,7 @@ 1 1 (% class="WordSection1" %) 2 2 ((( 3 - 3 += Overview = 4 4 5 -(% style="tab-stops:23.3pt" %)**OVERVIEW** 6 - 7 -(% class="MsoBodyText" style="margin-top:.45pt" %) 8 8 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. 9 9 10 10 ... ... @@ -11,12 +11,15 @@ 11 11 [[image:pos server.png]] 12 12 13 13 14 -* (% lang="EN-US" style="font-size:12pt; line-height:14.65pt; tab-stops:42.9pt 42.95pt" %)The third party host can be a single or dual host system. 15 -* (% lang="EN-US" style="font-size:12pt; line-height:14.65pt; tab-stops:42.9pt 42.95pt" %)PayEx has a fully redundant system, with an active/active configuration. 16 -* (% lang="EN-US" style="font-size:12pt; line-height:14.65pt; tab-stops:42.9pt 42.95pt" %)The third party host(s) connect to PayEx loadbalanser 17 17 18 -(% style="font-size:16px" %)Supported massage types 19 19 13 +The third party host can be a single or dual host system. 14 +PayEx has a fully redundant system, with an active/active configuration. 15 +The third party host(s) connect to PayEx loadbalanser 16 + 17 + 18 +== (% style="font-size:16px" %)Supported massage types (%%) == 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]] 22 22 |1110|PayEx|[[**A(% lang="EN-US" style="font-size:9pt; tab-stops:44.75pt" %)UTHORISATION REQUEST (%%)1100/1110**>>AUTHORISATION REQUEST 1100/1110]] ... ... @@ -38,9 +38,9 @@ 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 -(% style="tab-stops:29.4pt" %)**MESSAGE LAYOUT** 42 42 43 -(% class="MsoBodyText" style="margin-top:.45pt" %) 42 +== Message layout == 43 + 44 44 This section covers message types and fields supported by PayEx 45 45 46 46 ... ... @@ -70,7 +70,6 @@ 70 70 ** mm: Minutes, 00 through 59 71 71 ** ss: Seconds, 00 through 59 72 72 73 - 74 74 The “Type”-column can contain: 75 75 76 76 * a : Alphabetic character [a..z,A..Z]