Hide last authors
Kristian Lingsom 4.1 1 (% class="WordSection1" %)
2 (((
Kristian Lingsom 19.1 3 = Overview =
Kristian Lingsom 5.2 4
Dani Alexander Berentzen 30.24 5 The H2H PayEx link enables authorization and capture of card transactions. Depending on the card, PayEx is either a PSP or the end host (card issuer). The third party host acts as a gateway between payment terminals and PayEx.
Kristian Lingsom 5.2 6
7
Cecilie Tyldum 35.1 8 [[image:architecture.png]]
Kristian Lingsom 5.2 9
10
Kristian Lingsom 19.1 11 The third party host can be a single or dual host system.
12 PayEx has a fully redundant system, with an active/active configuration.
Dani Alexander Berentzen 30.23 13 The third party host(s) connects to a load balancer at PayEx.
Kristian Lingsom 19.1 14
15
Kristian Lingsom 20.1 16 == Supported massage types ==
Kristian Lingsom 19.1 17
Kristian Lingsom 4.1 18
Kristian Lingsom 21.1 19 |=Message Type|=Reference
Kristian Lingsom 23.1 20 |1100/1110|[[AUTHORISATION REQUEST>>doc:AUTHORISATION REQUEST 1100/1110]]
Kristian Lingsom 23.2 21 |1200/1210|[[FINANCIAL TRANSACTION REQUEST>>doc:.FINANCIAL TRANSACTION REQUEST 1200/1210.WebHome]]
22 |1220/1221/1230|[[FINANCIAL TRANSACTION ADVICE>>doc:FINANCIAL TRANSACTION ADVICE 1220/1221/1230]]
23 |1420/1421/1430|[[REVERSAL ADVICE>>doc:REVERSAL ADVICE 1420/1421/1430]]
24 |1820/1830|[[NETWORK MANAGEMENT>>doc:.NETWORK MANAGEMENT 1820/1830.WebHome]]
Pål-Eirik Askerød 30.3 25 |1520/1521/1530|RECONCILIATION REQUEST (**Currently not supported)**
Kristian Lingsom 4.1 26
Pål-Eirik Askerød 30.15 27 * Message types included in the table above are supported unless otherwise specified. E-g reconciliation is not currently supported.
28 Use links to different message types for details on specific messages.
Pål-Eirik Askerød 30.31 29 Only the Financial transaction advice (1220), Reversal Advice (1420) use repeat messages(1221 and 1421). Repeats are to be sent according to rules below.
30 * Advice can be declined by PayEx for technical reasons. 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 between retires. After 6 retry attempts have failed manual intervention by third party and PayEx support must be initiated.
Kristian Lingsom 4.1 31
Kristian Lingsom 19.1 32 == Message layout ==
33
Kristian Lingsom 16.1 34 This section covers message types and fields supported by PayEx
Kristian Lingsom 4.1 35
Kristian Lingsom 17.2 36
Kristian Lingsom 16.1 37 |=Presence|=Title|=Description
38 |C|Conditional|The data element’s presence depends on specific circumstances, witch are described either directly or by reference in the message content table.
39 |CE|Conditional echo|The response message must have the same data element if the data element was present in the original message
40 |M|Mandatory|Data element must be present in the specified message
41 |ME|Mandatory echo|The response message must have the same data element and value as sent in the original message request or advice message
42 |O|Optional|The data element may or may not be present in the message
Kristian Lingsom 17.2 43 )))
Kristian Lingsom 4.1 44
Pål-Eirik Askerød 30.15 45 Optional fields may always be present in requests, even when not needed. In such case, they will be ignored. Requests received missing a mandatory field will get action code 904 - Format Error.
Kristian Lingsom 17.2 46
47 The third party host must ignore unknown fields included in the response messages.
48
49 When no usage notes are given in the field description, the field should be used as described in IFSF [1].
50
51 The “Format”-column can contain following info:
52
53 * LL: Variable length field, max 99 bytes as data. The field contains 2 bytes holding the length of the data. Example: 303101 a one byte field with LL = 3031 and the data is 01.
54 * LLL: Variable length field, max 999 bytes as data. The field contains 3 bytes holding the length of the data. Example: 30303101 a one byte field with LLL = 303031 and the data is 01.
55 * Date/time field formats, YYMMDDhhmmss (or variations), where:
56 ** YY : Last 2 digits of the year, 00 through 99
57 ** MM: Month, 01 through 12.
58 ** DD: Day, 01 through 31
59 ** hh: Hour, 00 through 23
60 ** mm: Minutes, 00 through 59
61 ** ss: Seconds, 00 through 59
62
63 The “Type”-column can contain:
64
65 * a : Alphabetic character [a..z,A..Z]
66 * n : Numeric BCD-digit. [0..9]
67 * ans: alphabetic, numeric and special characters
68 * an : alphabetic and numeric.
69 * s : Special characters.
70 * b : Binary
71 * p: pad character, space
72 * x: “C” for credit, “D” for debit and shall always be associated with a numerical amount data element.
73
74 The “Size”-column can contain:
75
76 * Variable length fields have a size that looks like “..nn”, where nn is the maximum number of characters or bytes.
77 * A fixed length field has “n” as size content, with n the number of characters or bytes.
78
79 All fixed length “n” data elements are assumed to be right justified with leading zeroes. All other fixed length data elements are left justified with trailing spaces. In all “b” data elements, blocks of 8 bits are assumed to be left justified with trailing zeroes.
80
81
Kristian Lingsom 24.2 82 == Message protocol ==
Kristian Lingsom 17.2 83
Kristian Lingsom 24.2 84 All messages are transferred using TCP/IP sockets.
85
86 The message will be encapsulated in a transmission frame as follows:
87
88 * The first 4 digits contain the length of the message in ASCII (decimal value, most significant digit first). The length field includes all bytes from the first byte of the message ID up to the last byte of the last field.
89 * This 4-digit length field is immediately followed by the message ID, also in ASCII (decimal value, most significant digit first).
Dani Alexander Berentzen 30.26 90 * An 8 byte message bitmap, which is a binary field (not ASCII encoded).
Kristian Lingsom 24.2 91 * Message fields, which could be ASCII or binary encoded. The fields with format ‘n, ns, an, ans, anp or x’ are ASCII encoded, while the fields with format ‘b’ are binary encoded. The following conventions shall be applied to all data elements:
92 ** All fixed length numeric data element values shall be right justified with leading zeroes.
93 ** All fixed length data elements with alphabetic or special characters shall be left justified with trailing blanks.
94 ** All fixed length binary data elements shall be right justified with leading zeroes.
95 ** The position of a character or a bit in a data element shall be counted from the left beginning with one (1).(See also section 5.1 Attribute specification in [01])
96 ** No trailer is included.
97
98 Example: An imaginary message which consists only of a message ID “0300” and an empty bitmap (all zeros) will be transmitted as follows:
Kristian Lingsom 17.2 99
Kristian Lingsom 24.2 100
Kristian Lingsom 24.3 101 |=Length|=(((
102 Message ID
103 )))|=Bitmap
Kristian Lingsom 24.2 104 |=0x30 0x30 0x31 0x32|=0x30 0x33 0x30 0x30|=0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
105
Kristian Lingsom 24.3 106 Example: An 1820 message, without MAC, will be transmitted as follows: Message bytes (hex):
107 303035303138323002300101000000003039313031353238343133383239313030393039313031353238343138333130353130303331
108
109
110 |=Field|=Format|=Encoding|=Data|=Parsed
111 |Message Length|n|ASCII|30303530|0050
Dani Alexander Berentzen 30.26 112 |Message ID|n|ASCII|31383230|1820
Pål-Eirik Askerød 30.9 113 |Bitmap|b|Binary|0230010100000000|
Kristian Lingsom 24.3 114 |7 - Date/Time|n|ASCII|30393130313532383431|0910152841
115 |11 - STAN|n|ASCII|333832393130|382910
116 |12 - Date/Time|n|ASCII|303930393130313532383431|090910152841
117 |24 - Function code|n|ASCII|383331|831
Pål-Eirik Askerød 30.9 118 |33 - Forwarding institution identification code|n|ASCII|(((
119 30323135
120 )))|15
Kristian Lingsom 24.3 121
Pål-Eirik Askerød 30.19 122 The PayEx response timeout is set to 35 seconds. If after 35+1 seconds, no response has been received, the third party host needs to take the appropriate action based on the message type. (E.g. send a reversal)
Kristian Lingsom 24.3 123
Dani Alexander Berentzen 30.27 124 The third party host has the possibility to perform offline stand-in, thought this needs to be agreed with the individual card issuers. Otherwise the merchant might not be reimbursed.
Kristian Lingsom 24.3 125
Pål-Eirik Askerød 30.31 126 == ==
Pål-Eirik Askerød 30.13 127
Kristian Lingsom 25.1 128 == PIN Validation ==
129
Pål-Eirik Askerød 29.2 130 PayEx perform online PIN validation on payment cards where PayEx is the acquirer, on all other cartds PIN is validated by the third party acuirer. PayEx will not interpret P-22 Point-Of-Service code to determine if it needs to validate PIN or not on PayEx fuel cards, but 3rd patry aquirers might so it's good practice to use P-22 correctly.
Kristian Lingsom 25.1 131
132 Fields required for PIN validation are:
133
134 * P-48-14 – PIN encryption Methodology
135 * P-52 – PIN data
136 * P-53 – Security related information
137
Kristian Lingsom 32.1 138 (% class="wikigeneratedid" id="H-1" %)
Pål-Eirik Askerød 30.16 139 See [[security documentation>>doc:.PayEx IFSF H2H Security specification.WebHome]] for details.
Pål-Eirik Askerød 30.13 140
Pål-Eirik Askerød 30.7 141 == Security documentation ==
142
Pål-Eirik Askerød 30.22 143 Here you can find details regarding the security elements of this H2H integration.
Pål-Eirik Askerød 30.7 144
Pål-Eirik Askerød 30.13 145 __[[SECURITY SPECIFICATION>>doc:.PayEx IFSF H2H Security specification.WebHome]]__
Pål-Eirik Askerød 30.12 146
Pål-Eirik Askerød 30.21 147 == Response codes ==
148
149 Here you can find the response codes which may be returned from PayEx.
150
151 [[RESPONSE CODES>>doc:.Response codes.WebHome]]
152
Pål-Eirik Askerød 30.31 153 == ==
Pål-Eirik Askerød 30.21 154
Pål-Eirik Askerød 30.18 155 == Message field overview ==
Kristian Lingsom 26.1 156
157 **P-3 PROCESSING CODE**
158
Dani Alexander Berentzen 30.28 159 Code used to describe the effect of a transaction on the customer account and the accounts affected. Currently fixed 000000 : Goods and services
Kristian Lingsom 26.1 160
Pål-Eirik Askerød 30.13 161
Kristian Lingsom 26.1 162 **P-4 AMOUNT, TRANSACTION**
163
Dani Alexander Berentzen 30.29 164 The amount is a numeric value, expressed without a decimal separator. Where a minor unit of currency applies, the relevant minor unit data element indicates the number of decimal places in the relevant amount. Example : NOK 1 = 100
Kristian Lingsom 26.1 165
Pål-Eirik Askerød 30.13 166
Kristian Lingsom 26.1 167 **P-7 DATE AND TIME, TRANSMISSION**
168
169 Date and time of message transmission from the third party host.
170
Pål-Eirik Askerød 30.13 171
Kristian Lingsom 26.1 172 **P-11 SYSTEM TRACE AUDIT NUMBER**
173
Dani Alexander Berentzen 30.28 174 Number assigned by the third party host to assist in identifying a transaction uniquely. Range from 000001 to 999999. Every message must have a new STAN, repeats use the same STAN as the original message.
Pål-Eirik Askerød 30.13 175
176
Kristian Lingsom 26.1 177 **P-12 DATE AND TIME, LOCAL TRANSACTION**
178
179 Date and time of the transaction when performed on the POS.
180
Pål-Eirik Askerød 30.13 181
Kristian Lingsom 26.1 182 **P-22 POINT OF SERVICE DATA CODE**
183
184 A series of codes intended to identify terminal capability, terminal environment and presentation security data.
185
186
187 **P-24 FUNCTION CODE**
188
189 |=Function code|=Description
190 |101|Original authorization, amount estimated used in 1100
191 |200|Original financial request/advice Used in 1200/1220/1221
192 |201|Previously approved authorisation, amount the same Used in 1220/1221
193 |202|Previously approved authorisation, amount differs Used in 1220/1221
194 |400|Full reversal Used in 1420/1421
195 |831|Echo test Used in 1820
196
197 **P-25 MESSAGE REASON CODE**
198
199 |=reason code |=Description
Pål-Eirik Askerød 30.19 200 |1003|Card issuer unavailable
Kristian Lingsom 26.1 201 |1004|Terminal processed
Pål-Eirik Askerød 30.20 202 |1005|ICC processed
Kristian Lingsom 26.1 203 |1508|On-line forced by terminal
204 |4000|Customer cancellation
205 |4020|Invalid response, no action taken
206 |4021|Timeout waiting for response
207 |4351|Cancellation - unmatched signature
208
209 **P-30 ORIGINAL AMOUNT**
210
211 The original amount data element is a constructed element of two parts with a total of 24 positions:
212 a) Original amount transaction, n 12;
213 b) Original amount reconciliation, n 12.
214 Absence of data shall be indicated by zeroes. These parts shall be used when attempting to perform a partial approval and shall contain the original amounts.
215
Pål-Eirik Askerød 30.13 216
Kristian Lingsom 26.1 217 **P-33 FORWARDING INSTITUTION IDENTIFICATION CODE**
218
219 10 digit code identifying the 3rd patry host. Each 3rd party integrated with PayEx will be assigned a unique code that they are to use in all messages where P-33 is specified.
220
Pål-Eirik Askerød 30.13 221
Kristian Lingsom 26.1 222 **P-38 APPROVAL CODE**
223
224 Code assigned by the authorising institution indicating approval.
225
Pål-Eirik Askerød 30.13 226
Kristian Lingsom 26.1 227 **P-39 ACTION CODE**
228
Dani Alexander Berentzen 30.30 229 See action code page for codes that can be returned by PayEx.
Kristian Lingsom 27.1 230
Pål-Eirik Askerød 30.13 231
Kristian Lingsom 27.1 232 **P-41 Card acceptor terminal identification**
Dani Alexander Berentzen 30.30 233 Needs to be unique per POS terminal at the merchant site.
Kristian Lingsom 27.1 234
Pål-Eirik Askerød 30.13 235
Kristian Lingsom 27.1 236 **P-42 Card acceptor identification code**
237
238 8 digit unique ID provided by PayEx for each merchant.
239
Pål-Eirik Askerød 30.13 240
Kristian Lingsom 27.1 241 **P-43 Card acceptor name/location**
242
243 The name and location of the card acceptor.
244
Pål-Eirik Askerød 30.13 245
Kristian Lingsom 27.1 246 **P-48 MESSAGE CONTROL DATA ELEMENTS**
247 Used for the control of messages between the POS and the FEP. These are present in field 48 as a variable content data element. It uses a standard bit map to identify the specific data elements present in field 48. The format is LLLVAR with a maximum length of 999. The 8 byte bit map is the first item (element 48-0) in the data element.
248
249
Pål-Eirik Askerød 30.13 250 **P-48-4 BATCH/SEQUENCE NUMBER**
251
Kristian Lingsom 27.1 252 This field identifies the transactions associated with a particular settlement period. This number starts at one and increments with each Reconciliation.
253
254
Pål-Eirik Askerød 30.13 255 **P-48-8 CUSTOMER DATA**
256
Kristian Lingsom 27.1 257 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 fuelling, 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 (\). (Note: the LVAR method is not used for these entries.) The entire data element has a maximum length of 250 bytes and is parsed as an LLLVAR field.
258
259 |=Element|=Name|=Attribute|=Description
260 |48-8-1|Number of customer data fields|n2|Count of customer data entries to follow.Note: this value must be from 1 to 16.
261 |48-8-2|Type of customer data|an 1|Identifies the type of customer data entered. (see P48-8-2)
262 |48-8-3|Value of customer data|ans...99|Data entered by customer orcashier.
263
Kristian Lingsom 28.1 264 **P-48-8-2 TYPE OF CUSTOMER DATA**
Kristian Lingsom 27.1 265
Pål-Eirik Askerød 30.19 266 1 - Vehicle ID
Kristian Lingsom 28.1 267 3 - Driver ID
268 4 - Mileage
Pål-Eirik Askerød 30.19 269
Kristian Lingsom 27.1 270
Pål-Eirik Askerød 30.19 271 **P-48-9 TRACK II OF VEHICLE CARD**
Kristian Lingsom 27.1 272
Pål-Eirik Askerød 30.19 273 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.
Kristian Lingsom 27.1 274
275
Pål-Eirik Askerød 30.13 276 **P-48-14 PIN ENCRYPTION METHODOLOGY**
Pål-Eirik Askerød 30.5 277
Pål-Eirik Askerød 30.13 278 See [[security documentation>>doc:.PayEx IFSF H2H Security specification.WebHome]] section for details.
Pål-Eirik Askerød 30.5 279
Kristian Lingsom 27.1 280
281 **P-48-37 VEHICLE IDENTIFICATION ENTRY MODE**
282 Only present when a vehicle number is available (P48-8). Defines how the vehicle number was entered:
283
284 0 - Manual entry
285 1- On the Card
Pål-Eirik Askerød 30.19 286 2 - Automatic License Plate Recognition
Kristian Lingsom 27.1 287
Pål-Eirik Askerød 30.13 288
Kristian Lingsom 27.1 289 **P-48-38 PUMP LINKED INDICATOR**
290
Kristian Lingsom 28.1 291 Indicating whether the fuel pump reading is is linked to the payment terminal:
Kristian Lingsom 27.1 292 0 – Unspecified
293 1 – Pump-linked
294 2 – Pump not linked
295
296
297 **P-48-39 DELIVERY NOTE NUMBER**
298 Number allocated by the terminal given to the customer as printed on the ticket.
299
Pål-Eirik Askerød 30.13 300
Kristian Lingsom 27.1 301 **P-49 CURRENCY CODE , TRANSACTION**
302 All transactions are in local currency, as defined during system installation. Actual value is as defined by ISO 4217.
303
Pål-Eirik Askerød 30.13 304
Kristian Lingsom 27.1 305 **P-52 PIN DATA**
Kristian Lingsom 28.1 306
Pål-Eirik Askerød 30.13 307 See[[ security documentation>>doc:.PayEx IFSF H2H Security specification.WebHome]] section for details.
Kristian Lingsom 28.1 308
Pål-Eirik Askerød 30.13 309
Kristian Lingsom 28.1 310 **P-53 SECURITY RELATED CONTROL INFORMATION**
311
Pål-Eirik Askerød 30.13 312 See[[ security documentation>>doc:.PayEx IFSF H2H Security specification.WebHome]] section for details.
Kristian Lingsom 28.1 313
314
Kristian Lingsom 28.2 315 **P-56 ORIGINAL DATA ELEMENTS**
316
317 Data elements of original transaction which contains the original “message identifier”, original “STAN” and original “date and time – local transaction”. This must be present if the message is preceded by an 1100 Authorisation Request, it can be omitted if the message is as a result of a store and forward transaction.
Pål-Eirik Askerød 30.19 318 In Payment advice : Link to previous Authorization dialog
319 In reversal advice : Link to previous Authorization request or previous Payment request being reversed.
Kristian Lingsom 28.1 320
Kristian Lingsom 28.2 321
322 **P-62 PRODUCT SETS AND MESSAGE DATA**
323
324 This field contains allowed product sets and message data.
325
326 |=Number|=Name|=Format|=Attribute|=Description
327 |62| |n|3|LLLVAR length field. Sets the length of P-62 data
328 |62-1|Allowed products|ans|...99|LLVAR field, contains the products that are allowed
329 |62-2|Device text|n|1|For what device 62-3 is to be sent to
Dani Alexander Berentzen 30.29 330 |62-3|Message text|ans|...999|LLLVAR field. Display text
Kristian Lingsom 28.2 331
332 All subfields must be present when bit 62 is set. Field 62 shall not be sent if none of the three subfields need to be sent. If one of the subfields needs to be sent, all three subfields shall be sent.
333
Kristian Lingsom 28.3 334
335 **P-63 PRODUCT DATA**
336
337 This data element provides the detailed information on the products purchased or selected by the customer. The first two fields (63-1, 63-2) appear once per transaction. The next seven fields can be repeated up to 18 times.
338
Pål-Eirik Askerød 30.19 339 Each product is represented by seven fields: Product Code, Unit of Measure, Quantity, Unit Price, Amount, Tax code and Additional product code. The variable length fields and the succeeding entry are separated by a back-slash (\).
Kristian Lingsom 28.3 340 Unit price and amount may be negative or positive, but the sum of the amounts in the product data must equal the transaction amount.
341 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.
342 The value must be numeric. The number of fractional digits has a maximum of 4. The Amount field may have fractional digits. The number of fractional digits is specified by the currency code.
343
344 The list of sales items can contain a mixture of normal sales items and refund items. These are included in the online Host message as follows:
345
346
347 |=Number|=Format|=Field|=Description
348 |63|n 3|Product data|LLLVAR length field. Sets the length of P-63 data
349 |63-1|a 1|Service level|(((
350 S - Self-serve
351 F - Full serve
352 Space - Information not available
353 )))
354 |63-2|n 2|Number of products|Count of products (sale item) reported for this transaction.
355
356 Each Sales item consists of the following components:
357
358
359 |=Number|=Format|=Field|=Description
360 |63-3|n 3 |Product code|3-digit product code that defines the type of product sold
Pål-Eirik Askerød 30.13 361 |63-4|a 1 |Unit of measure|Indicates the meaning of the Quantity field. ‘U’ Sold per Unit
362 ‘O’ Unit of Measurement undefined ‘L’ Sold per Litre.
Kristian Lingsom 28.3 363 |63-5|n 9|Quantity|Number of product units
364 | | |Separator|‘\’ To separate Quantity from Unit-Price
365 |63-6|sn 9|Unit price|Starts with a Minus sign when Unit price is negative. First digit is exponent. Typically 3 for fuels, and 2 for shop articles. Remaining digits are actual unit price
366 | | |Separator|‘\’ To separate Unit price from Amount
367 |63-7|sn 12|Amount|Starts with a minus sign in case Item amount is negative. 2 decimals are always implied.
368 | | |Separator|‘\’ To separate the Amount from the Vat Code
369 |63-8|an 1|Tax code|1 digit VAT code
370 |63-9|n 14|Additional Product code|Up to 14 digits article number as known in the POS
Pål-Eirik Askerød 30.13 371 | | |Terminator |‘\’ To mark the end of this sales item
Kristian Lingsom 28.3 372
373 **P-64 MAC**
374
Pål-Eirik Askerød 30.14 375 See [[security documentation>>doc:.PayEx IFSF H2H Security specification.WebHome]] for details.
Kristian Lingsom 28.3 376
377
Pål-Eirik Askerød 30.11 378 **P-127 Encrypted data**
379
Pål-Eirik Askerød 30.13 380 This field contains the encrypted track2 data. See [[security documentation>>doc:.PayEx IFSF H2H Security specification.WebHome]] section for details on how to generate this field.
Pål-Eirik Askerød 30.14 381
Pål-Eirik Askerød 30.17 382
383 **P-128 MAC**
384
Pål-Eirik Askerød 30.19 385 **This field is used for MAC if P-127 is present**. See [[security documentation>>doc:.PayEx IFSF H2H Security specification.WebHome]] for details.