1430

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

3.4	1	For technical reasons an reversal advice can be declined if PayEx is unable to store the transaction. 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 with exponential wait time between retries. After 6 retry attempts have failed manual intervention by third party and PayEx support must be initiated.
3.1	2
2.1	3	REVERSAL ADVICE 1420/1421
	4
	5	Only fields listed below are supported.
	6
3.4	7	\|Element number\|(% style="width:205px" %)Data element name\|(% style="width:67px" %)Presence\|Format\|Type\|Size\|Usage notes
	8	\|3\|(% style="width:205px" %)Processing Code\|(% style="width:67px" %)M\| \|n\|6\|Fixed "000000". Other processing codes are currently not supported.
	9	\|4\|(% style="width:205px" %)Amount, transaction\|(% style="width:67px" %)M\| \|n\|12\|Amount of original message. Must be equal to original message P-4 value.
	10	\|7\|(% style="width:205px" %)Date and time, transmission\|(% style="width:67px" %)M\|(((
3.3	11	MMDDhhmmss
3.5	12	)))\|n\|10\|E.g.: 1025123020
	13	\|11\|(% style="width:205px" %)Systems trace audit number\|(% style="width:67px" %)M\| \|n\|6\|Assigned by third party host. Unique pr request
3.4	14	\|12\|(% style="width:205px" %)Date and time, local transaction\|(% style="width:67px" %)M\|(((
3.3	15	YYMMDDhhmmss
3.5	16	)))\|n\|12\|E.g.: 171025100515
3.4	17	\|24\|(% style="width:205px" %)Function code\|(% style="width:67px" %)M\| \|n\|3\|Fixed 400: Full reversal
	18	\|25\|(% style="width:205px" %)Message reason code\|(% style="width:67px" %)M\| \|n\|4\|(((
2.1	19	4000: Customer Cancellation.
	20
	21	4020: Invalid response, no action taken.
	22
	23	4021: Timeout waiting for response.
	24
	25	4351: Cancellation – unmatched signature
	26	)))
3.5	27	\|33\|(% style="width:205px" %)Forwarding Institution identification code\|(% style="width:67px" %)O\|LL\|n\|..11\|Unique id provided by PayEx used for all transactions from given 3rd party
3.4	28	\|38\|(% style="width:205px" %)Approval code\|(% style="width:67px" %)C\| \|anp\|6\|(((
3.3	29	Present if original transaction was approved
2.1	30	)))
3.6	31	\|41\|(% style="width:205px" %)Card acceptor terminal identification\|(% style="width:67px" %)M\| \|n\|8\|Needs to be unique per POS terminal at the merchant site. Must be equal to original message P-41
	32	\|42\|(% style="width:205px" %)Card acceptor identification code\|(% style="width:67px" %)M\| \|n\|15\|8 digit unique ID provided by PayEx for each merchant. Must be equal to original message P-42
3.4	33	\|48\|(% style="width:205px" %)Message control data elements\|(% style="width:67px" %)M\|LLL\|ans\|..999\|
	34	\|48-0\|(% style="width:205px" %)Bit map for data elements in bit 48\|(% style="width:67px" %)M\| \|b\|8\|
	35	\|48-4\|(% style="width:205px" %)Batch/sequence number\|(% style="width:67px" %)M\| \|n\|10\|Assigned by third party host.
3.5	36	\|49\|(% style="width:205px" %)Currency code\|(% style="width:67px" %)M\| \|an\|3\|Numeric currency code (ISO-4217 standard). E.g. "578" for NOK
5.1	37	\|53\|(% style="width:205px" %)Security Related Control Information\|(% style="width:67px" %)M\|LL\|b\|..48\|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.
3.4	38	\|56\|(% style="width:205px" %)Original data elements\|(% style="width:67px" %)M\|LL\|n\|..35\|(((
3.5	39	Contains Message Type Indicator(MTI), STAN and Transaction Date and Time from (% style="background-color:transparent" %)original message. E.g. Length 22 "(%%)1200 023576 171031174233 "
2.1	40
3.3	41	MTI is 4 digits, STAN (P-11) is 6 digits and Original transaction date/time(P-12) is in format "YYMMDDhhmmss"
2.1	42	)))
5.1	43	\|64\|(% style="width:205px" %)MAC\|(% style="width:67px" %)M\| \|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	44
	45	REVERSAL ADVICE RESPONSE 1430
	46
	47	\|Element number\|Data element name\|Presence\|Format\|Type\|Size\|Usage notes
3.1	48	\|2\|Primary account number\|ME\|LL\|ans\|..19\|
	49	\|3\|Processing Code\|ME\| \|n\|6\|
	50	\|4\|Amount, transaction\|ME\| \|n\|12\|
2.1	51	\|7\|Date and time, transmission\|M\|(((
3.3	52	MMDDhhmmss
3.1	53	)))\|n\|10\|
	54	\|11\|Systems trace audit number\|ME\| \|n\|6\|
2.1	55	\|12\|Date and time, local transaction\|ME\|(((
3.3	56	YYMMDDhhmmss
3.1	57	)))\|n\|12\|
	58	\|32\|Acquiring institution identification code\|ME\|LL\|n\|..11\|
3.3	59	\|38\|Approval code\|CE\| \|ans\|6\|Present if original transaction was approved
	60	\|39\|Action code\|M\| \|n\|3\|400 if accepted.
3.6	61	\|41\|Card acceptor terminal identification\|ME\| \|n\|8\|
	62	\|42\|Card acceptor identification code\|ME\| \|n\|15\|
3.1	63	\|48\|Message control data elements\|M\|LLL\|ans\|..999\|
	64	\|48-0\|Bit map for data elements in bit 48\|M\| \|b\|8\|
	65	\|48-4\|Batch/sequence number\|ME\| \|n\|10\|
	66	\|49\|Currency code, transaction\|ME\| \|an\|3\|
5.1	67	\|53\|Security Related Control Information\|M\|LL\|b\|..48\|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.
	68	\|64\|MAC\|M\| \|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.