Payment Service provider API ISO8583_2 ( IFSF) H2H description
Version 17.1 by Kristian Lingsom on 2017/10/16 12:38
OVERVIEW
The purpose of the H2H PayEx link is to enable authorization and settlement of card transactions, where PayEx is end host for that card, or just an PSP. The third party host acts as a gateway in between payment terminals and PayEx.
- The third party host can be a single or dual host system.
- PayEx has a fully redundant system, with an active/active configuration.
- The third party host(s) connect to PayEx loadbalanser
Supported massage types
| Type | Source | Reference |
| 1100 | 3rd party | AUTHORISATION REQUEST 1100/1110 |
| 1110 | PayEx | AUTHORISATION REQUEST 1100/1110 |
| 1200 | 3rd party | FINANCIAL TRANSACTION REQUEST 1200/1210 |
| 1210 | PayEx | FINANCIAL TRANSACTION REQUEST 1200/1210 |
| 1220 | 3rd party | FINANCIAL TRANSACTION ADVICE 1220/1221/1230 |
| 1221 | 3rd party | FINANCIAL TRANSACTION ADVICE 1220/1221/1230 |
| 1230 | PayEx | FINANCIAL TRANSACTION ADVICE 1220/1221/1230 |
| 1420 | 3rd party | REVERSAL ADVICE 1420/1421/1430 |
| 1421 | 3rd party | REVERSAL ADVICE 1420/1421/1430 |
| 1430 | PayEx | REVERSAL ADVICE 1420/1421/1430 |
| 1820 | 3rd party | NETWORK MANAGEMENT |
| 1830 | PayEx | NETWORK MANAGEMENT |
Message types not mentioned in the above table are not supported. E.g. reconciliation is not supported.
- Only the Financial transaction advice (1220), Reversal Advice (1420) use repeat messages. Repeats are to be sendt according to xxxxxxx rules
- Advices won’t be declined by PayEx unless for a technical reason.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 (to-be-defined). After 6 retry attemps have failed manual intervention by thirsd party and PayEx support must be initiated.
MESSAGE LAYOUT
This section covers message types and fields supported by PayEx
| Presence | Title | Description |
|---|---|---|
| C | Conditional | The data element’s presence depends on specific circumstances, witch are described either directly or by reference in the message content table. |
| CE | Conditional echo | The response message must have the same data element if the data element was present in the original message |
| M | Mandatory | Data element must be present in the specified message |
| ME | Mandatory echo | The response message must have the same data element and value as sent in the original message request or advice message |
| O | Optional | The data element may or may not be present in the message |