Last modified by Bjørnar Ruud on 2021/03/18 10:47
From version 30.14
edited by Pål-Eirik Askerød
on 2017/11/01 13:24
To version 30.15
edited by Pål-Eirik Askerød
on 2017/11/01 14:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -26,7 +26,8 @@
26 26  |1820/1830|[[NETWORK MANAGEMENT>>doc:.NETWORK MANAGEMENT 1820/1830.WebHome]]
27 27  |1520/1521/1530|RECONCILIATION REQUEST (**Currently not supported)**
28 28  
29 -* Message types included in the table above are supported unless specified. E-g reconciliation is not currently supported.
29 +* Message types included in the table above are supported unless otherwise specified. E-g reconciliation is not currently supported.
30 +Use links to different message types for details on specific messages.
30 30  Only the Financial transaction advice (1220), Reversal Advice (1420) use repeat messages. Repeats are to be sent according to xxxxxxx rules
31 31  * 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.
32 32  
... ... @@ -43,7 +43,7 @@
43 43  |O|Optional|The data element may or may not be present in the message
44 44  )))
45 45  
46 -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.
47 +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 get action code 904 - Format Error.
47 47  
48 48  The third party host must ignore unknown fields included in the response messages.
49 49