AUTHORIZATION REQUEST 1100

Element    numberData element namePresenceFormatTypeSizeUsage notes
3Processing CodeM n6Fixed 000000. Other processing code values are currently not supported.
4Amount, transactionM n12E.g.: 1 kr (NOK)  value="000000000100"
7Date and time, transmissionM

MMDDhhmmss

n10E.g.: 1025123020
11Systems trace audit numberM n6Assigned by third party host. Unique pr request
12Date and time, local transactionM

YYMMDDhhmmss

n12E.g.: 171025100515
22Point of service data codeM an12See table below for details on this field and sub-fields.
24Function codeM n3

Fixed 101: Original Authorization. Other values are currently not supported.

25Message reason codeM n4Fixed 1508. Online only
26Card acceptor business codeM n45541 for indoor and 5542 for outdoor
33Forwarding Institution identification codeMLLn..11Unique id provided by PayEx used for all transactions from given 3rd party
41Card acceptor terminal identificationM n8Needs to be unique per POS terminal at the merchant site.
42Card acceptor identification codeM n158 digit unique ID provided by PayEx for each merchant. 
48Message control data elementsMLLLans..999 
48-0Bit mapM b8 
48-4Batch/sequence numberM n10Assigned by third party host
48-8Customer dataCLLLans..250See table below for details on this field and sub-fields.
48-9Track II of vehicle cardOLLns..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-14PIN Encryption MethodologyC ans2Present if online PIN. See security documentation section for details. 
49Currency code, transactionM an3

Numeric currency code (ISO-4217 standard). E.g. "578" for NOK

52PIN DataC b8Present if online PIN. See security documentation section for details. 
53Security Related Control InformationMLLb..48See security documentation section for details.
61PIN KSNOLLLans20See security documentation section for details.
127Encrypted track2 dataMLLLb..999See security documentation section for details.
128MACM b8MAC field used when field 127 present. See security documentation section for details.

AUTHORIZATION RESPONSE 1110

Element    numberData element namePresenceFormatTypeSizeUsage notes
3Processing CodeME n6 
4Amount, transactionM n12Authorized amount. The amount available to customer
7Date and time, transmissionM

MMDDhhmmss

n10E.g.: 1022150534
11Systems trace audit numberME n6 
12Date and time, local transactionME

YYMMDDhhmmss

n12E.g.: 171025100515
30Original amountC n24Original amount if partial approval or decline.
32

Acquiring institution identification

code

MELLn..11 
38Approval codeC ans6If transaction has been approved.
39Action codeM n3Action code. See action code section for available codes.
41Card acceptor terminal identificationME n8 
42Card acceptor identification codeME n15 
48Message control data elementsMLLLans..999 
48-0Bit mapM b8 
48-4Batch/sequence numberME n10 
49Currency code, transactionME an3 
53Security Related Control InformationMLLb..48See security documentation section for details.
62Product setsCLLLans..999 
62-1Allowed product setsCLLans..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-2Device typeO n1 
62-3Message textOLLLans..894 
64MACM b8See 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 numberData element namePresenceFormatTypeSizeUsage 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 numberData element namePresenceFormatTypeSizeUsage notes
1

Pos 1: Card data input capabilities

M an1

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 an1

1: PIN
Y: Signature, plaintext/enciphered PIN offline and ‘no cvm’ capable, enciphered pin online

3Pos 3: Card capture capabilityM   0:None
T: None and SDA/DDA/CDA capable
4

Pos 4: Operating environment

M an1

1: On premises of card acceptor, attended  
2: On premises of card acceptor, unattended

5Pos 5: Cardholder presentM an10: Cardholder present
6Pos 6: Card presentM an11: Card present
7Pos 7: Card data input modeM an1

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

8Pos 8: Cardholder authentication methodM an10: Not authenticated
1: PIN
5: Manual signature verification
9Pos 9: Cardholder authentication entityM an1

0: Not authenticated

1: ICC

2: Card acceptor device

3: Authorizing Agent

10Pos 10: Card data output capabilityM an11: None
3: ICC
11Pos 11: Terminal output capabilityM an12: Printing
4: Printing and display
12Pos 12: PIN capture capabilityM an1

4: Four characters

C: Twelve characters

 

Tags:
Created by Helge Dahl on 2020/04/02 10:11