Wiki source code of NETWORK MANAGEMENT 1820/1830

Last modified by Helge Dahl on 2020/04/02 10:11

5.8	1	Message authentication code (MAC) is included on network management requests to validate the MAC key issued by PayEx. PayEx recommends that this message type is the first to be implemented and tested. This will at an early stage verify that both PayEx and 3rd party has the same MAC key.
5.1	2
5.8	3	Once the integration is done and in use the network massage can be used by both the 3rd party and PayEx to monitor that the hosts can communicate, e.g there are no network issues.
5.1	4
	5
3.1	6	NETWORK MANAGEMENT ADVICE 1820
2.1	7
4.1	8	\|Element number\|Data element name\|Presence\|(% style="width:109px" %)Format\|(% style="width:25px" %)Type\|Size\|Usage notes
	9	\|7\|Date and time, transmission\|M\|(% style="width:109px" %)(((
5.4	10	MMDDhhmmss
5.8	11	)))\|(% style="width:25px" %)n\|10\|E.g.: 1025123020
	12	\|11\|Systems trace audit number\|M\|(% style="width:109px" %) \|(% style="width:25px" %)n\|6\|Assigned by third party host. Unique pr request
4.1	13	\|12\|Date and time, local transaction\|M\|(% style="width:109px" %)(((
5.4	14	YYMMDDhhmmss
5.8	15	)))\|(% style="width:25px" %)n\|12\|E.g.: 171025100515
5.3	16	\|24\|Function code\|M\|(% style="width:109px" %) \|(% style="width:25px" %)n\|3\|831: System audit control / echo test. Other function codes are currently not supported.
	17	\|33\|(((
	18	Forwarding institution identification code
	19	)))\|M\|(% style="width:109px" %)LL\|(% style="width:25px" %)n\|..10\|(((
	20	Up to 10 digit code identifying the 3rd party host. Each 3rd party integrated with PayEx will be assigned a unique code that they are to use in all messages where P-33 is specified.
2.1	21	)))
7.1	22	\|53\|Security Related Control Information\|M\|(% style="width:109px" %)LL\|(% style="width:25px" %)b\|..48\|Specifies mac key version information. (53-1). See [[security documentation>>url:https://wiki.payex.com/xwiki/bin/view/Team%20Area/POS/Server/Documentation/POS/Payment%20Service%20provider%20API%20ISO8583_2%20%28%20IFSF%29%20H2H%20description/PayEx%20IFSF%20H2H%20Security%20specification/]] section for details.
	23	\|64\|MAC\|M\|(% style="width:109px" %) \|(% style="width:25px" %)b\|8\|See [[security documentation>>url:https://wiki.payex.com/xwiki/bin/view/Team%20Area/POS/Server/Documentation/POS/Payment%20Service%20provider%20API%20ISO8583_2%20%28%20IFSF%29%20H2H%20description/PayEx%20IFSF%20H2H%20Security%20specification/]] section for details.
2.1	24
3.1	25	NETWORK MANAGEMENT ADVICE RESPONSE 1830
2.1	26
	27	\|Element number\|Data element name\|Presence\|Format\|Type\|Size\|Usage notes
	28	\|7\|Date and time, transmission\|M\|(((
4.1	29	MMDDh hmmss
3.1	30	)))\|n\|10\|
	31	\|11\|Systems trace audit number\|ME\| \|n\|6\|
2.1	32	\|12\|Date and time, local transaction\|ME\|(((
	33	YYMMD
	34
	35	Dhhmm ss
3.1	36	)))\|n\|12\|
5.4	37	\|33\|(((
	38	Forwarding institution identification code
	39	)))\|ME\|LL\|n\|..11\|
5.6	40	\|39\|Action code\|M\| \|n\|3\|Fixed 800 if Accepted
5.5	41	\|53\|Security Related Control Information\|ME\|LL\|b\|..48\|
3.1	42	\|64\|MAC\|M\| \|b\|8\|