Please try searching something.
ISO8583 Issuing Gateway
General description
ISO8583 HTTP Gateway (Gateway) has been developed according to ISO8583 Native host-to-host Interface specification for processing issuing direction messages received from card suite solution and transform them to HTTP REST calls to pre-configured web-hook using JSON payload. In other words, it enables issuing customers to communicate with the Processing using REST service.
Gateway starts a new thread that listens on the configured server port and forwards all the non-technical messages to the customer in JSON format.
Deployment
Configure SSH host connectivity:
Parameter | Description |
---|---|
backend.url | Webhook endpoint URL that should be called upon receiving incoming message |
Payload specification
Field names used are the same as within ISO8583 Native host-to-host Interface specification.
For details on allowed field values/usage conditions etc., please refer to ISO8583 Native host-to-host Interface specification.
Request
{
“mti”:”mti”,
“fld_102”:“Account id (Account # that should be used for authorization execution)”,
“fld_002”:”Masked card number”,
“fld_003”:”Processing code”,
“fld_004”:”Amount, Transaction”,
“fld_005”:”Amount, reconcilation”,
“fld_006”:”Amount, cardholder billing”,
“fld_007”:”Date and time, transmission”,
“fld_010”:”Conversation rate, Cardholder billing”,
“fld_011”:”System Trace Audit Number",
“fld_012”:”Date and Time, Local Transaction”,
“fld_019”:”Country code, Acquirer institution”,
“fld_022”:”Point of service data code”,
“fld_024”:”Function code”,
“fld_025”:”Message Reason Code”,
“fld_026”:”Card Acceptor Business Code”,
“fld_030”:”Amount, original”,
“fld_031”:”Acquirer Reference Data”,
“fld_032”:”Acquirer Institution Identification Code”,
“fld_033”:”Forwarding Institution Code”,
“fld_037”:”Retrieval Reference Number”,
“fld_038”:”Approval Code”,
“fld_039”:”Response Code”,
“fld_040”:”Service Code”,
“fld_041”:”Card Acceptor terminal Identification”,
“fld_042”:”Card Acceptor Identification code”,
“fld_043”:”Card Acceptor name/Location”,
“fld_046”:”Amount, fees”,
“fld_049”:”Currency code, Transaction”,
“fld_050”:”Currency code, Reconcilation”,
“fld_051”:”Currency code, Cardholder billing”,
“fld_072”:”Additional e-commerce data”,
“fld_093”:”Transaction destination institution identification code”,
“fld_094”:”Transaction originator institution identification code”,
“fld_095”:”Card Issuer Reference number”,
“fld_098”:”Payee”,
“fld_100”:”Receiving institution Identification Code”,
“fld_104”:”Transaction description",
“fld_126”:”Acquirer request additional data”
}
Response
{
“mti”:”mti”,
“fld_102”:“account id from incoming request”,
“fld_003”:”Processing code from incoming request”,
“fld_011”:”System Trace Audit Number from incoming request”,
“fld_037”:”Retrieval Reference Number from incoming request”,
“fld_095”:”Card Issuer Reference number (from incoming request(if present) or own generated)”,
“fld_038”:”Approval Code”,
“fld_039”:”Response Code”
}
Jump to
- General description
- Deployment
- Payload specification