FINANCIAL TRANSACTION REQUEST 1200/1210
FINANCIAL TRANSACTION REQUEST 1200
Fields not described on the below table are not supported by PayEx
| 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) ="000000000100". Transaction amount in | |
| 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 | |
| 12 | Date and time, local transaction | M | YYMMDDhhmmss | n | 12 | E.g.: 171025100515 |
| 22 | Point of service data code | M | an | 12 | See table here for details. | |
| 24 | Function code | M | n | 3 | Fixed 200: Original financial request/advice. | |
| 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 3rd party | |
| 48-8 | Customer data | C | LLL | ans | ..250 | Only present if customer data entered. As specified here. |
| 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-37 | Vehicle identification entry mode | O | ans | 1 | Indicates how the vehicle identity has been determined: 2 - ALPR | |
| 48-38 | Pump linked indicator | O | n | 1 | Indicates whether the fuel pump reading is linked to the payment terminal: 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. | |
| 49 | Currency code, transaction | M | an | 3 | Numeric currency code (ISO-4217 standard). E.g. "578" for NOK | |
| 52 | PIN Data | C | b | 8 | Only for Online PIN. See security documentation section for details. | |
| 53 | Security Related Control Information | M | LL | b | ..48 | See security documentation section for details. |
| 55 | ICC System Related Data | C | LLL | b | ..250 | BER-TLV TAG format. We currently use EMV v4.3 Book 3 Application Specification. See Book 3 for details. |
| 63 | Product data | M | LLL | ans | ..999 | See description below for details on how to create this field. |
| 127 | Encrypted track2 data | M | LLL | b | ..999 | See security documentation section for details. |
| 128 | MAC | M | b | 8 | See security documentation section for details. |
FINANCIAL TRANSACTION RESPONSE 1210
The following fieds listed below are supported in the response message. Fields not listed are not supported.
| Element number | Data element name | Presence | Format | Type | Size | Usage notes |
| 3 | Processing Code | ME | n | 6 | ||
| 4 | Amount, transaction | M | n | 12 | ||
| 7 | Date and time, transmission | M | MMDDhhmmss | n | 10 | |
| 11 | Systems trace audit number | ME | n | 6 | ||
| 12 | Date and time, local transaction | ME | YYMMDDhhmmss | n | 12 | |
| 33 | Acquiring institution identification code | ME | LL | n | ..11 | |
| 38 | Approval code | C | anp | 6 | Present if transaction is 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 | ME | LLL | ans | ..999 | |
| 48-0 | Bit map | ME | b | 8 | ||
| 48-4 | Batch/sequence number | ME | n | 10 | ||
| 49 | Currency code, transaction | ME | an | 3 | ||
| 53 | Security Releated Control Info | ME | LL | b | ..48 | |
| 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 a 1210 response valid product codes are returned when the customer has violated a restriction. |
| 62-2 | Device type | O | n | 1 | ||
| 62-3 | Message text | O | LLL | ans | ..894 | |
| 64 | MAC | M | b | 8 |
P-63 Product data
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 (\).
Unit price and amount may be negative or positive, but the sum of the amounts in the product data must equal the transaction amount.
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.
P-63 Data elements for product data
The following fieds listed below are supported in the response message. Fields not listed are not supported.
| Element number | Data element name | Presence | Format | Type | Size | Usage notes |
| 1 | Service level | M | a | 1 | Type of sale. | |
| 2 | Number of products | M | n | 2 | Count of products reported for this transaction. | |
| 3 | Product code | M |
| n | 3 | Type of product sold. Length increased to be consistent with [2] |
| 4 | Unit of measure | M | a | 1 | Type of measurement. | |
| 5 | Quantity | n | ..9 | Number of product units sold. | ||
| 6 | Unit price | M | ns | ..9 | Price per unit of measure (signed). | |
| 7 | Amount | M | ns | ..12 | Monetary value of purchased product. The decimal point is implied by the optional currency code. The default value is two fractional decimal digits (signed). | |
| 8 | Tax code | M | an | 1 | Type of VAT included in amount. Amended to alphanumeric to provide more potential codes. | |
| 9 | Additional product code | O | n | ..14 | Optional - up to 14 digits code to identify product. |
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.)
Items purchased:
20.73 litres of Unleaded Fuel @ 9.12 NOK per litre (self-serve) Ten packs of Cigarettes @ 64.50 NOK per pack
Carton of milk @ 0.99 NOK (no tax)
The product codes used in this example are:
001 - Unleaded Fuel
011 - Cigarettes
061 - Groceries
089 - Deposit on bottles
See the following example of message data and the parsing of the data field.
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 \