AUTHORISATION REQUEST 1100/1110

Version 3.1 by hde on 2020/02/19 09:26

AUTHORIZATION REQUEST 1100

Element number	Data element name	Presence	Format	Type	Size	Usage notes
3	Processing Code	M		n	6	Fixed 000000. Other processing code values are currently not supported.
4	Amount, transaction	M		n	12	E.g.: 1 kr (NOK) value="000000000100"
7	Date and time, transmission	M	MMDDhhmmss	n	10	E.g.: 1025123020
11	Systems trace audit number	M		n	6	Assigned by third party host. Unique pr request
12	Date and time, local transaction	M	YYMMDDhhmmss	n	12	E.g.: 171025100515
22	Point of service data code	M		an	12	See table below for details on this field and sub-fields.
24	Function code	M		n	3	Fixed 101: Original Authorization. Other values are currently not supported.
25	Message reason code	M		n	4	Fixed 1508. Online only
26	Card acceptor business code	M		n	4	5541 for indoor and 5542 for outdoor
33	Forwarding Institution identification code	M	LL	n	..11	Unique id provided by PayEx used for all transactions from given 3rd party
41	Card acceptor terminal identification	M		n	8	Needs to be unique per POS terminal at the merchant site.
42	Card acceptor identification code	M		n	15	8 digit unique ID provided by PayEx for each merchant.
48	Message control data elements	M	LLL	ans	..999
48-0	Bit map	M		b	8
48-4	Batch/sequence number	M		n	10	Assigned by third party host
48-8	Customer data	C	LLL	ans	..250	See table below for details on this field and sub-fields.
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.
48-14	PIN Encryption Methodology	C		ans	2	Present if online PIN. See security documentation section for details.
49	Currency code, transaction	M		an	3	Numeric currency code (ISO-4217 standard). E.g. "578" for NOK
52	PIN Data	C		b	8	Present if online PIN. See security documentation section for details.
53	Security Related Control Information	M	LL	b	..48	See security documentation section for details.
127	Encrypted track2 data	M	LLL	b	..999	See security documentation section for details.
128	MAC	M		b	8	MAC field used when field 127 present. See security documentation section for details.

AUTHORIZATION RESPONSE 1110

Element number	Data element name	Presence	Format	Type	Size	Usage notes
3	Processing Code	ME		n	6
4	Amount, transaction	M		n	12	Authorized amount. The amount available to customer
7	Date and time, transmission	M	MMDDhhmmss	n	10	E.g.: 1022150534
11	Systems trace audit number	ME		n	6
12	Date and time, local transaction	ME	YYMMDDhhmmss	n	12	E.g.: 171025100515
30	Original amount	C		n	24	Original amount if partial approval or decline.
32	Acquiring institution identification code	ME	LL	n	..11
38	Approval code	C		ans	6	If transaction has been approved.
39	Action code	M		n	3	Action code. See action code section for available codes.
41	Card acceptor terminal identification	ME		n	8
42	Card acceptor identification code	ME		n	15
48	Message control data elements	M	LLL	ans	..999
48-0	Bit map	M		b	8
48-4	Batch/sequence number	ME		n	10
49	Currency code, transaction	ME		an	3
53	Security Related Control Information	M	LL	b	..48	See security documentation section for details.
62	Product sets	C	LLL	ans	..999
62-1	Allowed product sets	C	LL	ans	..99	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. In an 1110 response they indicate the product sets the customer can purchase, before the purchase.
62-2	Device type	O		n	1
62-3	Message text	O	LLL	ans	..894
64	MAC	M		b	8	See security documentation section for details.

P-48-8 Customer data

The customer data is any data entered by the customer or cashier as required by the authorizer to complete the transaction. Transactions requiring customer data may be related to fleet fueling, cheque authorizations or any other type of retail store management functions. Up to sixteen separate entries are supported. Each entry consists of two elements, the type of customer data entered and the variable length value of the entered data. Successive entries are separated by a back-slash (\). The entire data element has a maximum length of 250 bytes and is parsed as an LLLVAR field. Currently supported sub-fields are listed below.

Element number	Data element name	Presence	Format	Type	Size	Usage notes
1	VEHICLE ID	O		an	..10
3	DRIVER ID	O		an	..8
4	ODOMETER READING	O		n	..8	Odometer reading in kilometers.

Example P-48-8:

"025 03 1 654321 \ 3 123456 \ 4 5000000"

P-22 POINT OF SERVICE DATA CODE

Element number	Data element name	Presence	Format	Type	Size	Usage notes
1	Pos 1: Card data input capabilities	M		an	1	2: magnetic stripe read 5: ICC A: RFID B: Magnetic stripe reader and key entry C: Magnetic stripe reader, ICC and key entry D: Magnetic stripe reader and ICC
2	Pos 2: Cardholder authentication capability	M		an	1	1: PIN Y: Signature, plaintext/enciphered PIN offline and ‘no cvm’ capable, enciphered pin online
3	Pos 3: Card capture capability	M				0:None T: None and SDA/DDA/CDA capable
4	Pos 4: Operating environment	M		an	1	1: On premises of card acceptor, attended 2: On premises of card acceptor, unattended
5	Pos 5: Cardholder present	M		an	1	0: Cardholder present
6	Pos 6: Card present	M		an	1	1: Card present
7	Pos 7: Card data input mode	M		an	1	2: Magnetic stripe read 3: Bar code 5: ICC 6: Key entered A: RFID C: ICC data captured and passed unaltered D: Magnetic stripe read following failed chip card read
8	Pos 8: Cardholder authentication method	M		an	1	0: Not authenticated 1: PIN 5: Manual signature verification
9	Pos 9: Cardholder authentication entity	M		an	1	0: Not authenticated 1: ICC 2: Card acceptor device 3: Authorizing Agent
10	Pos 10: Card data output capability	M		an	1	1: None 3: ICC
11	Pos 11: Terminal output capability	M		an	1	2: Printing 4: Printing and display
12	Pos 12: PIN capture capability	M		an	1	4: Four characters C: Twelve characters

Tags:

Created by hde on 2020/02/19 09:15