Debit Host Interface ISO8583

Download as pdf or txt
Download as pdf or txt
You are on page 1of 12

DEBIT HOST INTERFACE

Technical Specifications
Version 0.1

i
TECHNICAL SPECIFICATIONS – DEBIT INTERFACE

Author Revision Revision Reason Document Ref


Date

Card Tech Services Ltd. ii


TECHNICAL SPECIFICATIONS – DEBIT INTERFACE

1. Introduction ......................................................................................................................................... 4
1.1 Background ................................................................................................................................................4
2 Communication ................................................................................................................................... 4
2.1 TCP Header................................................................................................................................................4
2.2 Physical Layer ............................................................................................................................................4
3 Message Flow ...................................................................................................................................... 5
3.1 Authorization Request...............................................................................................................................5
3.2 Authorization Request card not in database ...........................................................................................5
3.3 Authorization Request Non Financial Check Failure.............................................................................5
3.4 Authorization Request Host Timeout ......................................................................................................6
3.5 Reversal Request........................................................................................................................................6
3.6 ATM Confirmation....................................................................................................................................6
4 Message Details ................................................................................................................................... 7
4.1 Message Identifier......................................................................................................................................7
4.2 Bitmap.........................................................................................................................................................7
4.3 0100 Authorization request .......................................................................................................................7
4.4 0110 Authorization Response....................................................................................................................8
4.5 0400 Reversal Request ...............................................................................................................................9
4.6 0410 Reversal Response.............................................................................................................................9
Appendix A – Field Description .............................................................................................................. 10

Card Tech Services Ltd. 3


TECHNICAL SPECIFICATIONS – DEBIT INTERFACE

1. Introduction
This document specifies the communication, message flow and field description for the debit interface between the
online authorization and the Debit Host.

1.1 Background
The online system is designed to accept authorization requests for card residing on host that the Bank will perform
financial (OTB) checking only. Given that a BIN is specified in online as a debit BIN, then if the card is loaded in the
system it then will check all non financial details of the card and then forward that request to an escape process
,described within, for financial checking. If the requested card was not loaded in online’s database then it will
forward it to the escape process without any checking. Further reference to this is the authorization process described
in the online manual.

2 Communication
The communication Protocol used for this interface will be TCP/IP. The service number and Host IP is parameterized.
Also the TCP/IP library used can be configured to work in “Server” or “Client” mode. Note that there is going to be
only one TCP connection kept open at all times, for all the traffic. This debit interface will send multiple requests
before responses are received.

2.1 TCP Header


Since the TCP/IP cannot identify a message start and end a message header length has to be used. The Header
consists of an optional start character defaulted to 0xFF, and five characters length is ASCII. The start characters can
be of any value or removed, but cannot be 0x00.

Start Character Length Indicator Data

2.2 Physical Layer


The physical layer is limited only by the SCO Unix driver availability. Usual implementations are over Ethernet,
Token Ring or PPP (Point to Point Protocol) over a serial line.

Card Tech Services Ltd. 4


TECHNICAL SPECIFICATIONS – DEBIT INTERFACE

3 Message Flow

3.1 Authorization Request

Visa or Local 0100 Non Financial 0100 Debit 0100 Host


Acquirer Checks - Engine
0110
0110

Authorization Request card in online database.

3.2 Authorization Request card not in database

Visa 0100 Non Financial 0100 Debit Host


Checks - Engine

0110
(Decline)

When a card does not exist in the online database the engine will forward the request to the debit interface.
Optionally the debit interface will send the request to the Host or decline.

3.3 Authorization Request Non Financial Check Failure

0100
Visa Non Financial Debit Host
Checks - Engine
0110

Card Tech Services Ltd. 5


TECHNICAL SPECIFICATIONS – DEBIT INTERFACE

3.4 Authorization Request Host Timeout

0100 0100 0100


Visa or Local Non Financial Debit Host
Acquirer Checks - Engine

0110 (decline)
0110
0420
0430

When the Host timeout, parameterized timeout value, a decline is generated. Upon the reception of a 0110 approval
the debit interface will generate a 0420 reversal.

3.5 Authorization Advice Request

Visa 0120 Non Financial 0120 Debit 0120 Host


Checks - Engine
0130
0110

Authorization Request card in online database.

3.6 Reversal Advice Request

Visa or Local 0420 Non Financial 0420 Debit 0420 Host


Acquirer Checks - Engine

0430 0430

3.7 ATM Confirmation

Visa or Local 0102 Non Financial 0102 Debit 0420 Host


Acquirer Checks - Engine

0430

Card Tech Services Ltd. 6


TECHNICAL SPECIFICATIONS – DEBIT INTERFACE

4 Message Details
The Message format is based on the ISO 8583, 1987 standard (version 0).

Message Bitmap Data


Identifier

4.1 Message Identifier

The message identifiers supported for this implementation are:

0100
0110
0120
0130
0420
0430

the identifier is two bytes long in BCD (Binary Coded Decimal) or packed format.

4.2 Bitmap

The bitmap is 8 bytes long. The first bit of this map indicates the existence of the secondary bitmap, which if it exists
it directly follows this one. The secondary bitmap is again 8 bytes long with each bitmap representing the existence of
64 fields. The primary and secondary bitmaps (if any) are in Hex format.

4.3 0100 Authorization request

Bit Description Type Comment


2 Pan (2) 19, ASCII
3 Processing Code 6, ASCII
4 Amount 12, ASCII
7 Transmission Date, Time GMT 10, ASCII
18 MCC 4, ASCII
32 Acquirer Institution (2) 11, ASCII
37 Retrieval Reference 12, ASCII
41 Terminal ID 8, ASCII
42 Acceptor ID 15, ASCII
43 Acceptor Name Location 40, ASCII
49 Currency 3, ASCII
102 Account To (2) 28, ASCII

Card Tech Services Ltd. 7


TECHNICAL SPECIFICATIONS – DEBIT INTERFACE

4.4 0110 Authorization Response

Bit Description Type Comment


2 Pan (2) 19, ASCII Same as request
3 Processing Code 6, ASCII Same as request
4 Amount 12, ASCII Same as request
7 Transmission Date, Time GMT 10, ASCII Same as request
18 MCC 4, ASCII Same as request
32 Acquirer Institution (2) 11, ASCII Same as request
37 Retrieval Reference 12, ASCII Same as request
38 Authorization Code 6, ASCII Only on approval
39 Authorization Response 2, ASCII
49 Currency 3, ASCII Same as request
54 Additional amount (2) 40, ASCII Present on Balance inquiry
102 Account To (2) 28, ASCII Same as request

4.5 0120 Authorization Advice Request

Bit Description Type Comment


2 Pan (2) 19, ASCII
3 Processing Code 6, ASCII
4 Amount 12, ASCII
7 Transmission Date, Time GMT 10, ASCII
18 MCC 4, ASCII
32 Acquirer Institution (2) 11, ASCII
37 Retrieval Reference 12, ASCII
38 Authorization Code 6, ASCII
39 Authorization Response 2, ASCII
41 Terminal ID 8, ASCII
42 Acceptor ID 15, ASCII
43 Acceptor Name Location 40, ASCII
49 Currency 3, ASCII
102 Account To (2) 28, ASCII

4.6 0130 Authorization Advice Response

Bit Description Type Comment


2 Pan (2) 19, ASCII Same as request
3 Processing Code 6, ASCII Same as request

Card Tech Services Ltd. 8


TECHNICAL SPECIFICATIONS – DEBIT INTERFACE

4 Amount 12, ASCII Same as request


7 Transmission Date, Time GMT 10, ASCII Same as request
18 MCC 4, ASCII Same as request
32 Acquirer Institution (2) 11, ASCII Same as request
37 Retrieval Reference 12, ASCII Same as request
38 Authorization Code 6, ASCII Only on approval
39 Authorization Response 2, ASCII
49 Currency 3, ASCII Same as request
102 Account To (2) 28, ASCII Same as request

4.7 0420 Reversal Advice Request

Bit Description Type Comment


2 Pan (2) 19, ASCII Same as original
3 Processing Code 6, ASCII Same as original
4 Amount 12, ASCII Same as original
7 Transmission Date, Time GMT 10, ASCII
18 MCC 4, ASCII Same as original
32 Acquirer Institution (2) 11, ASCII Same as original
37 Retrieval Reference 12, ASCII Same as original
38 Authorization Code 6, ASCII Same as original
49 Currency 3, ASCII
95 Replacement Amount 42, ASCII Only in Partial Reversals
102 Account To (2) 28, ASCII Same as original

4.8 0430 Reversal Advice Response

Bit Description Type Comment


2 Pan (2) 19, ASCII Same as request
3 Processing Code 6, ASCII Same as request
4 Amount 12, ASCII Same as request
7 Transmission Date, Time GMT 10, ASCII
18 MCC 4, ASCII Same as request
32 Acquirer Institution (2) 11, ASCII Same as request
37 Retrieval Reference 12, ASCII Same as request
38 Authorization Code 6, ASCII Same as request
39 Authorization Response 2, ASCII

Card Tech Services Ltd. 9


TECHNICAL SPECIFICATIONS – DEBIT INTERFACE

49 Currency 3, ASCII Same as request


95 Replacement Amount 42, ASCII Same as request
102 Account To (2) 28, ASCII Same as request

Appendix A – Field Description


Field 2 - Primary Account Number
Attribute: an 19, LLVAR

Field 3 - Processing Code


Attribute: n6

Positions 1,0 identify the transaction type


00 – Purchase
01 – Cash / Cash withdrawal
30 – Balance Inquiry

Positions 3,4 Account from


00 – Not used

Positions 5,6 Account To


00 – Not specified

Field 4 - Amount
Attribute: n 12

The authorization amount with implied decimal digits. This is expressed in the currency identified by field 49. For
this implementation the interface will convert all requests to a specified currency, that of field 49.

Field 7 – Transmission Date Time


Attribute: n 10

This is the transmission date time expressed in GMT with the format MMDDhhmmss.

Field 18 – Merchant Type (MCC)


Attribute: n4

This is the merchant type as identified by the acquirer.

Field 32 – Acquirer Institution ID


Attribute: n … 11, LLVAR

This is the acquirer institution ID as assigned by the Payment systems.

Field 37 – Retrieval Reference Number


Attribute: n 12

The retrieval reference is a reference number for the acquirer for this authorization. This is the same in subsequent
reversals.

Card Tech Services Ltd. 10


TECHNICAL SPECIFICATIONS – DEBIT INTERFACE

Field 38 – Authorization Number


Attribute: an 6
Authorization code generated by the Host for this approval. This is not necessarily correctly present in the
reversal as some acquirer may fill this with an incorrect value. For OnUs acquired Transactions this field will
contain the value of the authorization response.

Field 39 – Authorization Response Code


Attribute: an 2

The response to the authorization request. Possible values are


00 Approved
01 Refer to Issuer
02 Refer to Issuer – Special condition
04 Pick Up Card
05 Do not honor
06 Error
07 Pick Up – Special Condition
14 Card Does Not Exist
41 Pick Up – Lost Card
43 Pick Up – Stolen Card
51 Not sufficient funds
62 Restricted card
77 Unable to locate original

Field 41 – Terminal Id
Attribute: ans 8

Field 42 – Merchant Id
Attribute: ans 15

Field 43 – Merchant Location City


Attribute: ans 40

The merchant location details are as follows:


1-25 Card Acceptor name
26-38 Merchant City
39-40 Two digit alphanumeric Country code

Field 49 – Currency Code


Attribute: n3

This is the currency defined in the interface parameters as the currency of communication with the host. The
interface will convert all incoming requests using the exchange rates in online.

Field 54 – Additional Amounts


Attribute: ans 120, LLLVAR

This filed is present as a response to the balance inquiry. It may include one or two amounts of 20 character long
format with the format being as follows.
1-2 Account type
00 Not specified
3-4 Amount type
Card Tech Services Ltd. 11
TECHNICAL SPECIFICATIONS – DEBIT INTERFACE

01 Ledger or OTB
02 Balance
5-7 Currency code
8 Amount sign
D –Debit
C – Credit
9-20 Amount
Decimal digits implied

Field 95 – Replacement amount


Attribute: an 42

This is the replacement amount (with implied decimal digits) in partial reversals in the currency specified by field 4.

Field 102 – From Account

Attribute: an 28, LLVAR

Card Tech Services Ltd. 12

You might also like