All fixed length numeric data element values shall be right justified with leading zeroes.The following conventions shall be applied to all data elements: The fields with format ‘n, ns, an, ans, anp or x’ are ASCII encoded, while the fields with format ‘b’ are binary encoded. Message fields, which could be ASCII or binary encoded.An 8 byte message bitmap, which is a binary field (not ASCII encoded).This 4-digit length field is immediately followed by the message ID, also 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. The first 4 digits contain the length of the message in ASCII (decimal value, most significant digit first).The message will be encapsulated in a transmission frame as follows: In all “b” data elements, blocks of 8 bits are assumed to be left justified with trailing zeroes.Īll messages are transferred using TCP/IP sockets. All other fixed length data elements are left justified with trailing spaces. A fixed length field has “n” as size content, with n the number of characters or bytes.Īll fixed length “n” data elements are assumed to be right justified with leading zeroes.
Variable length fields have a size that looks like “.nn”, where nn is the maximum number of characters or bytes.x: “C” for credit, “D” for debit and shall always be associated with a numerical amount data element.ans: alphabetic, numeric and special characters.YY : Last 2 digits of the year, 00 through 99.Date/time field formats, YYMMDDhhmmss (or variations), where:.Example: 30303101 a one byte field with LLL = 303031 and the data is 01. The field contains 3 bytes holding the length of the data.
LLL: Variable length field, max 999 bytes as data.Example: 303101 a one byte field with LL = 3031 and the data is 01. The field contains 2 bytes holding the length of the data. LL: Variable length field, max 99 bytes as data.The “Format”-column can contain following info: When no usage notes are given in the field description, the field should be used as described in IFSF. The third party host must ignore unknown fields included in the response messages.
Requests received missing a mandatory field will get action code 904 - Format Error. Optional fields may always be present in requests, even when not needed. The data element may or may not be present in the message The response message must have the same data element and value as sent in the original message request or advice message The response message must have the same data element if the data element was present in the original messageĭata element must be present in the specified message The data element’s presence depends on specific circumstances, witch are described either directly or by reference in the message content table. This section covers message types and fields supported by PayEx
After 6 retry attempts have failed manual intervention by third party and PayEx support must be initiated. It’s expected that the third party implement a retry delay with exponential wait period between retires. In this case the third party host need to retry the advice until manual intervention or the advice has been accepted. Advice can be declined by PayEx for technical reasons.Repeats are to be sent according to rules below. Only the Financial transaction advice (1220), Reversal Advice (1420) use repeat messages(12). Use links to different message types for details on specific messages. E-g reconciliation is not currently supported.