Wiki source code of FINANCIAL TRANSACTION REQUEST 1200/1210

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

2.1	1	FINANCIAL TRANSACTION REQUEST 1200
	2
	3	Fields not described on the below table are not supported by PayEx
	4
	5	\|Element number\|Data element name\|Presence\|Format\|Type\|Size\|Usage notes
2.3	6	\|3\|Processing Code\|M\| \|n\|6\|Fixed 000000. Other processing code values are currently not supported.
2.7	7	\|4\|Amount, transaction\|M\| \|n\|12\|E.g.: 1 kr (NOK) ="000000000100". Transaction amount in
2.1	8	\|7\|Date and time, transmission\|M\|(((
2.3	9	MMDDhhmmss
2.7	10	)))\|n\|10\|E.g.: 1025123020
2.2	11	\|11\|Systems trace audit number\|M\| \|n\|6\|Assigned by third party host
2.1	12	\|12\|Date and time, local transaction\|M\|(((
2.3	13	YYMMDDhhmmss
2.7	14	)))\|n\|12\|E.g.: 171025100515
6.1	15	\|22\|Point of service data code\|M\| \|an\|12\|See table [[here>>doc:Main.POS.Payment Service provider API ISO8583_2 ( IFSF) H2H description.AUTHORISATION REQUEST 1100/1110\|\|anchor="HP-22POINTOFSERVICEDATACODE"]] for details.
2.3	16	\|24\|Function code\|M\| \|n\|3\|Fixed 200: Original financial request/advice.
	17	\|25\|Message reason code\|M\| \|n\|4\|Fixed 1508. Online only
2.2	18	\|26\|Card acceptor business code\|M\| \|n\|4\|5541 for indoor and 5542 for outdoor.
2.7	19	\|33\|Forwarding Institution identification code\|M\|LL\|n\|..11\|Unique id provided by PayEx used for all transactions from given 3rd party
2.8	20	\|41\|Card acceptor terminal identification\|M\| \|n\|8\|Needs to be unique per POS terminal at the merchant site.
	21	\|42\|Card acceptor identification code\|M\| \|n\|15\|8 digit unique ID provided by PayEx for each merchant.
2.2	22	\|48\|Message control data elements\|M\|LLL\|ans\|..999\|
	23	\|48-0\|Bit map\|M\| \|b\|8\|
	24	\|48-4\|Batch/sequence number\|M\| \|n\|10\|Assigned by 3^^rd ^^party
6.1	25	\|48-8\|Customer data\|C\|LLL\|ans\|..250\|Only present if customer data entered. As specified [[here>>doc:Main.POS.Payment Service provider API ISO8583_2 ( IFSF) H2H description.AUTHORISATION REQUEST 1100/1110\|\|anchor="HP-48-8Customerdata"]].
2.3	26	\|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.
	27	\|48-37\|Vehicle identification entry mode\|O\| \|ans\|1\|(((
	28	Indicates how the vehicle identity has been determined:
	29	0 - Manual entry
	30	1 - On the card
	31
	32	2 - ALPR
	33	)))
	34	\|48-38\|Pump linked indicator\|O\| \|n\|1\|(((
	35	Indicates whether the fuel pump reading is linked to the payment terminal:
	36	0 - Unspecified
	37	1 - Pump-linked
	38
	39	2 - Pump not linked
	40	)))
	41	\|48-39\|Delivery note number\|O\| \|n\|10\|(((
2.7	42	Number allocated by the terminal given to the customer. ((% style="background-color:transparent" %)POS ticket number). Unique number pr transaction.
2.3	43	)))
2.7	44	\|49\|Currency code, transaction\|M\| \|an\|3\|Numeric currency code (ISO-4217 standard). E.g. "578" for NOK
4.1	45	\|52\|PIN Data\|C\| \|b\|8\|Only for Online PIN. 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.
	46	\|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.
2.3	47	\|55\|(((
	48	ICC System Related Data
2.4	49	)))\|C\|LLL\|b\|..250\|(((
	50	BER-TLV TAG format. We currently use EMV v4.3 Book 3 Application Specification. See Book 3 for details.
	51	)))
6.1	52	\|63\|Product data\|M\|LLL\|ans\|..999\|See [[description below>>doc:Main.POS.Payment Service provider API ISO8583_2 ( IFSF) H2H description.FINANCIAL TRANSACTION REQUEST 1200/1210.WebHome\|\|anchor="HP-63Productdata"]] for details on how to create this field.
4.1	53	\|127\|Encrypted track2 data\|M\|LLL\|b\|..999\|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.
	54	\|128\|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.
2.1	55
	56	FINANCIAL TRANSACTION RESPONSE 1210
	57
	58	The following fieds listed below are supported in the response message. Fields not listed are not supported.
	59
	60	\|Element number\|Data element name\|Presence\|Format\|Type\|Size\|Usage notes
2.2	61	\|3\|Processing Code\|ME\| \|n\|6\|
	62	\|4\|Amount, transaction\|M\| \|n\|12\|
2.1	63	\|7\|Date and time, transmission\|M\|(((
2.5	64	MMDDhhmmss
2.2	65	)))\|n\|10\|
	66	\|11\|Systems trace audit number\|ME\| \|n\|6\|
2.1	67	\|12\|Date and time, local transaction\|ME\|(((
2.5	68	YYMMDDhhmmss
2.2	69	)))\|n\|12\|
2.5	70	\|33\|Acquiring institution identification code\|ME\|LL\|n\|..11\|
2.2	71	\|38\|Approval code\|C\| \|anp\|6\|(((
	72	Present if transaction is approved
2.1	73	)))
4.1	74	\|39\|Action code\|M\| \|n\|3\|Action code. See [[action code section>>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/Response%20codes/]] for available codes.
2.8	75	\|41\|Card acceptor terminal identification\|ME\| \|n\|8\|
	76	\|42\|Card acceptor identification code\|ME\| \|n\|15\|
2.5	77	\|48\|Message control data elements\|ME\|LLL\|ans\|..999\|
	78	\|48-0\|Bit map\|ME\| \|b\|8\|
2.2	79	\|48-4\|Batch/sequence number\|ME\| \|n\|10\|
	80	\|49\|Currency code, transaction\|ME\| \|an\|3\|
2.5	81	\|53\|Security Releated Control Info\|ME\|LL\|b\|..48\|
2.2	82	\|62\|Product sets\|C\|LLL\|ans\|..999\|
2.3	83	\|62-1\|Allowed product sets\|C\|LL\|ans\|..99\|(((
	84	This data element provides the information on the product sets that the customer is permitted to select. Each product set is represented by 3 bytes, sent to POS.
	85
	86	In a 1210 response valid product codes are returned when the customer has violated a restriction.
	87	)))
2.2	88	\|62-2\|Device type\|O\| \|n\|1\|
	89	\|62-3\|Message text\|O\|LLL\|ans\|..894\|
	90	\|64\|MAC\|M\| \|b\|8\|
2.3	91
2.10	92	==== ====
2.3	93
2.4	94	==== P-63 Product data ====
2.3	95
	96	Each product is represented by seven fields: Product Code, Unit of Measure, Quantity, Unit Price, Amount, Taxcode and Additional product code. The variable length fields and the succeeding entry are separated by a back-slash (\).
	97
	98	Unit price and amount may be negative or positive, but the sum of the amounts in the product data must equal the transaction amount.
	99
	100	The values of Quantity and Unit price may have a value that includes both integer and fractional values. The format of these fields consists of a single digit, which specifies the number of fractional digits following the integer, followed by the numeric value. The value must be numeric. The Amount field may have fractional digits. The number of fractional digits is specified by the currency code.
	101
	102	P-63 Data elements for product data
	103
	104	The following fieds listed below are supported in the response message. Fields not listed are not supported.
	105
	106	\|Element number\|Data element name\|Presence\|Format\|Type\|Size\|Usage notes
	107	\|1\|Service level\|M\| \|a\|1\|(((
	108	Type of sale.
	109	S - Self-serve
	110	F - Full serve
	111	Space - Information not available
	112	)))
	113	\|2\|(((
	114	Number of products
	115	)))\|M\| \|n\|2\|(((
	116	Count of products reported for this transaction.
	117	)))
	118	\|3\|(((
	119	Product code
	120	)))\|M\|(((
	121
	122	)))\|n\|3\|(((
	123	Type of product sold. Length increased to be consistent with [2]
	124	)))
	125	\|4\|(((
	126	Unit of measure
	127	)))\|M\| \|a\|1\|(((
	128	Type of measurement.
	129	)))
	130	\|5\|(((
	131	Quantity
	132	)))\| \| \|n\|..9\|(((
	133	Number of product units sold.
	134	)))
	135	\|6\|(((
	136	Unit price
	137	)))\|M\| \|ns\|..9\|(((
	138	Price per unit of measure (signed).
	139	)))
	140	\|7\|(((
	141	Amount
	142	)))\|M\| \|ns\|..12\|(((
	143	Monetary value of purchased product. The decimal point is implied by the optional currency code. The default value is two fractional decimal digits (signed).
	144	)))
	145	\|8\|(((
	146	Tax code
	147	)))\|M\| \|an\|1\|(((
	148	Type of VAT included in amount. Amended to alphanumeric to provide more potential codes.
	149	)))
	150	\|9\|(((
	151	Additional product code
	152	)))\|O\| \|n\|..14\|(((
	153	Optional - up to 14 digits code to identify product.
	154	Length has increased to be consistent with proposed international standards on product code identification.
	155	)))
	156
	157	The following example depicts a sale of the three products described below plus a bottle return to recover the deposit. The total length of the data element is 89 characters. (Note: the length is included in the example for completeness. The data in the example are separated by a space for readability.)
	158	Items purchased:
	159	20.73 litres of Unleaded Fuel @ 9.12 NOK per litre (self-serve) Ten packs of Cigarettes @ 64.50 NOK per pack
	160	Carton of milk @ 0.99 NOK (no tax)
	161	The product codes used in this example are:
	162	001 - Unleaded Fuel
	163
	164	011 - Cigarettes
	165	061 - Groceries
	166	089 - Deposit on bottles
	167
	168	See the following example of message data and the parsing of the data field.
	169	Example: 089 S 04 001 L 22073 \ 2912 \ 18906 \ 0 \ 011 U 010 \ 26450 \ 64500 \ 0 \ 061 O ~\~\ 99 \ 0 12345 \ 089 U 03 \ -2250 \ - 750 \0 54321 \
	170