PayEx Developer Portal - FINANCIAL TRANSACTION ADVICE 1220/1221/1230

1

For technical reasons an 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 period. After 6 retry attempts have failed manual intervention by third party and PayEx support must be initiated.

2

3

4

**FINANCIAL TRANSACTION ADVICE 1220/1221**

5

6

7

|3|Processing Code|M| |n|6|Fixed 000000. Other processing code values are currently not supported.

8

|4|Amount, transaction|M| |n|12|E.g.: 1 kr (NOK) ="000000000100".

9

|7|Date and time, transmission|M|(((

10

MMDDhhmmss

11

)))|n|10|E.g.: 1025123020

12

|11|Systems trace audit number|M| |n|6|Assigned by third party host

13

|12|Date and time, local transaction|M|(((

14

YYMMDDhhmmss

15

)))|n|12|E.g.: 171025100515

16

|22|Point of service data code|M| |an|12|See table [[here>>url:https://wiki.payex.com/xwiki/wiki/external/view/POS/Payment%20Service%20provider%20API%20ISO8583_2%20%28%20IFSF%29%20H2H%20description/AUTHORISATION%20REQUEST%C2%A01100%2F1110#HP-22POINTOFSERVICEDATACODE]] for details.

17

|24|Function code|M| |n|3|(((

18

200: Standing in for Card Issuer

19

20

201: Previously approved authorisation

21

22

202: Previously approved authorization (amount differs)

23

)))

24

|25|Message reason code|M| |n|4|(((

25

1003: Card Issuer unavailable

26

27

1004:Terminal processed

28

)))

29

|26|Card acceptor business code|M| |n|4|5541 for indoor and 5542 for outdoor

30

|33|Forwarding Institution identification code|O|LL|n|..11|Unique id provided by PayEx used for all transactions from given 3rd party

31

|38|Approval code|M| |anp|6|Copied from original approved authorisation response if available. Otherwise 000000

32

|39|Action code|M| |n|3|(((

33

Copied from approved authorisation, or 000 when

approved offline.

)))

|41|Card acceptor terminal identification|M| |n|8|Needs to be unique per POS terminal at the merchant site.

38

|42|Card acceptor identification code|M| |n|15|8 digit unique ID provided by PayEx for each merchant.

39

|48|Message control data elements|M|LLL|ans|..999|

40

|48-0|Bit map|M| |b|8|

41

|48-4|Batch/sequence number|M| |n|10|Assigned by Third party host

42

|48-8|Customer data|C|LLL|ans|..250|As specified [[here>>url:https://wiki.payex.com/xwiki/wiki/external/view/POS/Payment%20Service%20provider%20API%20ISO8583_2%20%28%20IFSF%29%20H2H%20description/AUTHORISATION%20REQUEST%C2%A01100%2F1110#HP-48-8Customerdata]].

43

|48-9|Track II of vehicle card|O|LL|ns|..37|Used to specify the second card in a transaction if a special card is needed in addition to the payment card to link a transaction to a loyalty account.

44

|48-38|Pump linked indicator|O| |n|1|(((

45

Indicates whether the fuel pump reading is linked to the payment terminal:

0 - Unspecified

1 - Pump-linked

2 - Pump not linked

)))

|48-39|Delivery note number|O| |n|10|Number allocated by the terminal given to the customer. (POS ticket number). Unique number pr transaction.

52

|49|Currency code, transaction|M| |an|3|Numeric currency code (ISO-4217 standard). E.g. "578" for NOK

53

|53|Security Related Control Information|M|LL|b|..48|See [[security documentation>>url:https://wiki.payex.com/xwiki/wiki/external/view/POS/Payment%20Service%20provider%20API%20ISO8583_2%20%28%20IFSF%29%20H2H%20description/PayEx%20IFSF%20H2H%20Security%20specification/]] section for details.

54

|56|Original Data Elements|C|LL|n|..35|(((

55

Not present if stand-in authorized (P-24 with value 200).

56

57

Contains Message Type Indicator (MTI), STAN and Transaction Date and Time from original message. E.g. Length 22 "1200 023576 171031174233 "

58

59

MTI is 4 digits, STAN (P-11) is 6 digits and Original transaction date/time(P-12) is in format "YYMMDDhhmmss".

60

)))

61

|63|Product data|M|LLL|ans|..999|See [[description below>>url:https://wiki.payex.com/xwiki/wiki/external/view/POS/Payment%20Service%20provider%20API%20ISO8583_2%20%28%20IFSF%29%20H2H%20description/FINANCIAL%20TRANSACTION%20REQUEST%C2%A01200%2F1210/#HP-63Productdata]] for details on how to create this field.

62

|127|Encrypted track2 data|M|LLL|b|..999|See [[security documentation>>url:https://wiki.payex.com/xwiki/wiki/external/view/POS/Payment%20Service%20provider%20API%20ISO8583_2%20%28%20IFSF%29%20H2H%20description/PayEx%20IFSF%20H2H%20Security%20specification/]] section for details.

63

|128|MAC|M| |b|8|See [[security documentation>>url:https://wiki.payex.com/xwiki/wiki/external/view/POS/Payment%20Service%20provider%20API%20ISO8583_2%20%28%20IFSF%29%20H2H%20description/PayEx%20IFSF%20H2H%20Security%20specification/]] section for details.

64

65

**{{id name="_bookmark35"/}}FINANCIAL TRANSACTION ADVICE RESPONSE 1230**

66

67

|**Element number**|**Data element name**|{{id name="_bookmark36"/}}**Presence**|**Format**|**Type**|**Size**|**Usage notes**

68

|3|Processing Code|ME| |n|6|

69

|4|Amount, transaction|ME| |n|12|

70

|7|Date and time, transmission|M|(((

MMDDh

hmmss

)))|n|10|

|11|Systems trace audit number|ME| |n|6|

76

|12|Date and time, local transaction|ME|(((

YYMMD

Dhhmm ss

)))|n|12|

|33|Forwarding Institution identification code|ME|LL|n|..11|Unique id provided by PayEx used for all transactions from given 3rd party

82

|38|Approval code|CE| |anp|6|

83

|39|Action code|M| |n|3|Action code. See [[action code section>>url:https://wiki.payex.com/xwiki/wiki/external/view/POS/Payment%20Service%20provider%20API%20ISO8583_2%20%28%20IFSF%29%20H2H%20description/Response%20codes/]] for available codes.

84

|41|Card acceptor terminal identification|ME| |n|8|

85

|42|Card acceptor identification code|ME| |n|15|

86

|48|Message control data elements|ME|LLL|ans|..999|

87

|48-0|Bit map|ME| |b|8|

88

|48-4|Batch/sequence number|ME| |n|10|

89

|49|Currency code, transaction|ME| |an|3|