bank-linked system channel specificatin. 2 features of bank-linked channel 1. securities firm and...

Bank-linked SystemChannel Specificatin

2

Features of Bank-linked Channel

1. SECURITIES FIRM and BANK retain 2 TCP channels. (One for sending & the other for receiving respectively)

- The channels are connected to the respective sending and receiving Port

2.The BANK initiates connection to the SECURITIES FIRM through its sending and receiving channel.

- SECURITIES FIRM acts as a Server, and BANK as a Client

3. Request message from originating party is sent via sending channel,

and response message to the request is received via receiving channel.

*Sending party receives acknowledge message after it sends request message via sending channel

*Sending party receives response message for the result from receiving party via receiving channel

*The messages sent by sending channel include both request message and response message

3

Channel Formation & Flowchart (When Securities Firm is an originating party -- Bank’s receiving channel)

BANK Channel(Receiving)

BANK Backend System

SECURI-TIES

Channel(Sending)

SECURI-TIES Back-

end System

BizProcessBiz

Process

1. TCP Connect: Bank always initiates connection. (Securities Firm serves as a Server, BANK serves as a Client)2. Heartbeat Request: Securities Firm sends ‘Heartbeat’ message to keep connected at 10-second interval, when there is no message to send. Heartbeat Acknowledgment: Bank sends acknowledging message.3.Transaction Request: Securities Firm sends business message. Transaction Acknowledgment: Bank sends acknowledging message. Transaction Response : Bank sends the result after processing the request via Bank’s sending channel.4. TCP Disconnect : Any party may terminate connection.

TCP Connect

Heartbeat Request/ Heartbeat AcknowledgementSessionMessage

BusinessMessage

Transaction Request

TCP Disconnect

Transaction Acknowledgement

SECURI-TIES

Channel(Receiving)

BANK Chan-

nel(Send-

ing)Transaction Response(BANK’s sending channel)


4

Channel formation and flowchart (When Bank is an originating party -- Bank’s sending channel)

BANK Channel(Sending)

BANK Backend System

SECURITIES Channel(Receiving)

SECURITIES Backend System

BizProcessBiz

Process

1. TCP Connect: Bank always initiates connection. ( Securities Firm serves as a Server, BANK serves as a Client)2. Heartbeat Request: Bank sends ‘Heartbeat’ message to keep connected at 10-second interval, when there is no message to send. Heartbeat Acknowledgement: Securities Firm sends acknowledging message.3.Transaction Request : Bank sends business message. Transaction Acknowledgement : Securities Firm sends acknowledging message. Transaction Response : Securities Firm sends the result after processing the request via Bank’s receiving channel . 4. TCP Disconnect : Any party may terminate connection.

TCP Connect

Heartbeat Request/Heartbeat AcknowledgmentSessionMessage

BusinessMessage

Transaction Request

TCP Disconnect

Transaction Acknowledgment

SECURITIES Channel(Sending)

BANK Channel(Receiving)

Transaction Response(Bank’s Receiving Channel)


5

Detailed Transaction Flowchart (When Securities Firm is an originating party)

BANK (Re-ceiving)SECURITIES

(Sending)

Receiving Channel of Bank

① Transaction Request

② Transaction Acknowledgement

BANK (Sending)SECURITIES

(Receiving)

Sending Channel of Bank

④ Transaction Acknowledgement

③ Transaction Response

* Transaction numbers are generated by Securities Firm. (Those sequential numbers given to the individual transactions are

unique for each day, but RE-request message must use the same number that was given to the original request message)

* Transaction number of Response should be identical to that of Request.

6

Detailed Transaction Flowchart (When Bank is an originating party)

BANK (Sending)SECURITIES

(Receiving)

Sending Channel of Bank

② Transaction Acknowledgement

① Transaction Request


BANK (Re-ceiving)SECURITIES

(Sending)

Receiving Channel of Bank

③ Transaction Response

④ Transaction Acknowledgement

* Transaction numbers are generated by Bank (Those sequential numbers given to the individual transactions for each

day are unique, but RE-request message must use the same number that was given to the original request message.)

7

Common Header

FieldNo.

Items Mode Length Position

Message Set

RemarksRequest Response

1 Length of Message N 4 0 ○ ○ Total Length including Data Part

2 Sender AN 1 4 ○ ◎ B : Bank, S : Securities Firm

3 Sending Institution Code AN 4 5 ○ ◎ Message Sending Institution Code: The code given to Bank, Securities Firm

4 S/R Flag A 1 9 ○ ◎ S.Send, R.Response, A.Ack

5 Message Type N 4 10 ○ ◎ Refer to Message Type

6 Message classification N 4 14 ○ ◎ Refer to Message Classification

7 Transaction Reference Number

N 10 18 ○ ○ Transaction Code given to Sending Institu-tion on transaction date

8 Message sending date N 14 28 ○ ◎ YYYYMMDDHHMISS

9 Response Code AN 4 42 ◎ Refer to Response Code

10 Transaction Date N 8 46 ○ ○ YYYYMMDD

11 FILLER AN 46 54 ○ ○

Total Length 100 Total Length of Common Part

8

Message Type & Message Classification

Message Types Operational Messages : Such transactional messages as deposit/withdrawal, inquiry, and cancellation, etc

Managerial Messages : The messages for system management(initiation, close, failure etc)

Message types Request Re-request Response

Operational Message 0200 0201 0210

Managerial Message 0800 0801 0810

Message classification Message classification to perform working-level operation Securities Firm : Bank : Bilateral : ◆ ◇ ◈

Managerial messages refer to individual part messages, not such message classification as initiation, close, disorder, etc

Message Type Messages Classification CodeCancellation of Messages

classificationinstitution

Operational Mes-sages

(0200/0210)

Inquiry of Bank Account Balance 1100 ◆

Inquiry of Securities Account 1200 ◇

Deposit Notice 2100 4100 ◇

Withdrawal Confirmation Request 2200 4200 ◇

Transaction Tally(Count) Request 3100 ◈

Managerial Mes-sages

(0800/0810)

Network Management 1100 ◈

Heartbeat 2000 ◈

9

Response Code

Type Code Code Name Remark

operation

0000 Normal1001 Invalid Account No1002 Invalid account name 1003 Invalid currency1004 Insufficient balance1005 Invalid amount ex> -0000001234.12

1006 Invalid account password1007 Invalid Bank Code1008 Deposit is not allowed1009 Withdrawal is not allowed1090 Unable to cancel1099 Etc Processing Error

Management

9001 Before Business Hour (Before Initiating Operation)9002 System Failure9003 After Business Hour (Operation Closed)

10

Session Message Format (Example)

Type No. Field Name Format Value Description

Header

1 Message Length N(4) 0100 Common Header Size + Data Size (ex : 0400)

2 Sender Institution Type AN(1) B B.Bank, S.Securities

3 Sender Institution Code N(4) 0001 Sender Institution Code (ex : 0001)

4 Send/Response Flag AN(1) S S.Send

5 Message Type N(4) 0800 message type

6 Message Classification N(4) 2000 message classfication

7 Transaction Number N(10) 0000000000 Transaction Sequence (All Zero)

8 Message Sending Time N(14) 20100711121212 YYYYMMDDHHMISS

9 Response Code AN(4) 4 Space

10 Transaction Date N(8) 20100711 YYYYMMDD

11 Filler AN(46) 46 Space

Heartbeat Request (from Bank)

Heartbeat Acknowledgement (from Securities)


Header




4 Send/Response Flag AN(1) A A. Acknowledgement



7 Transaction Number N(10) 0000000000 Transaction Sequence (All Zero)





<Sending Channel of Bank>

<Sending Channel of Bank>

Acknowledging message is sent by returning the original request message in which only the value of ‘Send/Response Flag’ field is set to ‘A,’ whereas the values of other fields in the original request message are unchanged (‘Send/Response Flag’ field is composing the Header of Request Message.)

11


Transaction Request : Inquiry of Securities Account (from Bank)


Header




4 Send/Response Flag AN(1) S S.Send



7 Transaction Number N(10) 0000000001 Transaction Sequence





Body

12 Bank Code AN(4) 0001

13 Bank Account Number AN(16) 123456

14 Inquiry Type AN(1) N N.Normal case, D. deposit case, W. withdrawal case

15 Account Name AN(120) 120 Space

16 Currency AN(1) 1 Space

17 Withdrawable Amount N(15) 15 Space


<Sending Channel of bank>

12



Header




4 Send/Response Flag AN(1) A A.Ack








Transaction Acknowledgement (From Securities) – Only Header <Sending Channel of Bank>


13

Session Messge Format (Example)

Transaction Response : Inquiry of Securities Account (from Securites)


Header


2 Sender Institution Type AN(1) S B.Bank, S.Securities


4 Send/Response Flag AN(1) R R.Response


6 Message Classification N(4) 1200 message classification

7 Transaction Number N(10) 0000000001 Transaction Sequence (Copy of Request)


9 Response Code AN(4) 0000



Body

12 Bank Code AN(4) 0001

13 Bank Account Number AN(16) 123456

14 Inquiry Type AN(1) N

15 Account Name AN(120) Jim

16 Currency AN(1) D D.USD, R.KHR

17 Withdrawable Amount N(15) 000001234567890 if US dollar, 000000012345.12


* Upon receipt of response message, the receiving party checks response code and processes it (If the response code is ‘0000,’

‘normal’ response is processed. Otherwise, ‘error’ response is processed.)

<Receiving Channel of Bank>


14



Header


2 Sender Institution Type AN(1) S B.Bank, S.Securities


4 Send/Response Flag AN(1) A A. Acknowledgement





9 Response Code AN(4) 0000



Transaction Acknowledgement (From Bank) – Only Header <Receiving Channel of Bank>


bank-linked system channel specificatin. 2 features of bank-linked channel 1. securities firm and...

Documents