Last modified by Bjørnar Ruud on 2021/03/18 10:47
From version 17.1
edited by Kristian Lingsom
on 2017/10/16 12:38
To version 17.2
edited by Kristian Lingsom
on 2017/10/16 12:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,7 +4,7 @@
4 4  
5 5  (% style="tab-stops:23.3pt" %)**OVERVIEW**
6 6  
7 -(% style="margin-top:.45pt" class="MsoBodyText" %)
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  
... ... @@ -15,7 +15,6 @@
15 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 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 -
19 19  (% style="font-size:16px" %)Supported massage types
20 20  
21 21  |Type|Source|Reference
... ... @@ -32,7 +32,7 @@
32 32  |1820|3rd party|[[(% style="tab-stops:35.55pt" %)**N**(% lang="EN-US" style="font-size:9pt; tab-stops:35.55pt" %)**ETWORK **(% style="tab-stops:35.55pt" %)**M**(% lang="EN-US" style="font-size:9pt; tab-stops:35.55pt" %)**ANAGEMENT**>>doc:.Network Management.WebHome]]
33 33  |1830|PayEx|[[(% style="tab-stops:35.55pt" %)**N**(% lang="EN-US" style="font-size:9pt; tab-stops:35.55pt" %)**ETWORK **(% style="tab-stops:35.55pt" %)**M**(% lang="EN-US" style="font-size:9pt; tab-stops:35.55pt" %)**ANAGEMENT**>>doc:.Network Management.WebHome]]
34 34  
35 -(% style="margin-top:0cm; margin-right:7.6pt; margin-bottom:.0001pt; margin-left:6.9pt" class="MsoBodyText" %)
34 +(% class="MsoBodyText" style="margin-top:0cm; margin-right:7.6pt; margin-bottom:.0001pt; margin-left:6.9pt" %)
36 36  Message types not mentioned in the above table are not supported. E.g. reconciliation is not supported.
37 37  
38 38  
... ... @@ -41,9 +41,10 @@
41 41  
42 42  (% style="tab-stops:29.4pt" %)**MESSAGE LAYOUT**
43 43  
44 -(% style="margin-top:.45pt" class="MsoBodyText" %)
43 +(% class="MsoBodyText" style="margin-top:.45pt" %)
45 45  This section covers message types and fields supported by PayEx
46 46  
46 +
47 47  |=Presence|=Title|=Description
48 48  |C|Conditional|The data element’s presence depends on specific circumstances, witch are described either directly or by reference in the message content table.
49 49  |CE|Conditional echo|The response message must have the same data element if the data element was present in the original message
... ... @@ -50,4 +50,45 @@
50 50  |M|Mandatory|Data element must be present in the specified message
51 51  |ME|Mandatory echo|The response message must have the same data element and value as sent in the original message request or advice message
52 52  |O|Optional|The data element may or may not be present in the message
53 +)))
53 53  
55 +Optional fields may always be present in requests, even when not needed. In such case, they will be ignored. Requests received missing a mandatory field will be 904 - Format Error.
56 +
57 +The third party host must ignore unknown fields included in the response messages.
58 +
59 +When no usage notes are given in the field description, the field should be used as described in IFSF [1].
60 +
61 +The “Format”-column can contain following info:
62 +
63 +* LL: Variable length field, max 99 bytes as data. The field contains 2 bytes holding the length of the data. Example: 303101 a one byte field with LL = 3031 and the data is 01.
64 +* LLL: Variable length field, max 999 bytes as data. The field contains 3 bytes holding the length of the data. Example: 30303101 a one byte field with LLL = 303031 and the data is 01.
65 +* Date/time field formats, YYMMDDhhmmss (or variations), where:
66 +** YY : Last 2 digits of the year, 00 through 99
67 +** MM: Month, 01 through 12.
68 +** DD: Day, 01 through 31
69 +** hh: Hour, 00 through 23
70 +** mm: Minutes, 00 through 59
71 +** ss: Seconds, 00 through 59
72 +
73 +
74 +The “Type”-column can contain:
75 +
76 +* a : Alphabetic character [a..z,A..Z]
77 +* n : Numeric BCD-digit. [0..9]
78 +* ans: alphabetic, numeric and special characters
79 +* an : alphabetic and numeric.
80 +* s : Special characters.
81 +* b : Binary
82 +* p: pad character, space
83 +* x: “C” for credit, “D” for debit and shall always be associated with a numerical amount data element.
84 +
85 +The “Size”-column can contain:
86 +
87 +* Variable length fields have a size that looks like “..nn”, where nn is the maximum number of characters or bytes.
88 +* A fixed length field has “n” as size content, with n the number of characters or bytes.
89 +
90 +All fixed length “n” data elements are assumed to be right justified with leading zeroes. All other fixed length data elements are left justified with trailing spaces. In all “b” data elements, blocks of 8 bits are assumed to be left justified with trailing zeroes.
91 +
92 +
93 +
94 +