PARTY B / RECEIVER DESIGNATED BANK ACCOUNT DETAILS:

*IP-to-IP / *Server-to-Server / *DTC

COMPANY NAME:
COMPANY ADDRESS:
REPRESENTED BY:
POSITION:
BANK NAME:
BANK ADDRESS:
SWIFT CODE:
BANK ID:
ACCOUNT TYPE:
ACCOUNT NAME:
ACCOUNT No. :
IBAN CODE [EUR]:
BIC/SWIFT CODE:
ACCOUNT SIGNATORY:
CLIENT’S NATIONALITY:
PASSPORT NUMBER:
PLACE OF ISSUE:
DATEOF ISSUANCE:
DATEOF EXPIRATION:
BANK OFFICER NAME :
BANK OFFICER PHONE :
BANK OFFICER EMAIL :
CLEARING HOUSE CODE:
GLOBAL SERVER IP:
GLOBAL SERVER ID:
IDENTITY CODE:
UTR:
SOURCE TRANSACTION CODE
ID:
REFERENCE NO. :    
UNIQUE TRANSACTION NO.
(UTR) :
COMMON ACCOUNT NO. :
SORT CODE:           
RECEIVING SERVER IP :
RECEIVING SERVER ID :
TERMINAL ID :
FARM :
WTS SERVER :        
HTS SERVER :  
USER NAME :
USER ID:
LOGON DORMAIN:
LOGON SERVER :
PERMIT ARRIVAL MONEY No:
CURRENCY:
In brief definition, we summarize these Interbank System Transfers : IP-to-IP
(IP/IP) and Server-to-Server (S2S) and DTC fund transfers as below;

• We define BANK A as the source and sender of the funds and BANK B as
the receiver of the funds.

• BANK A has the funds in form of (cash) in one of its customer’s A/c that
is the SENDER ACCOUNT NAME and Number.

• BANK B has two different account number types. The first account
number type is the BANK’s COMMON ACCOUNT; this is the gateway
account of the Bank that receives funds that arrives as a result of
interbank system transfers. The second A/c number type is the regular
customer A/c (Company/Business/Corporation/Individual).

• BANK B A/c technical details are provided so that Bank A can initiate the
transfer.

• The names of the BANK B A/c corresponding bank officers, along with
their direct bank telephone line numbers and their email addresses are to
be provided.

• BANK A as the sender party initiates the fund transfer session that will
deliver the funds from the source Account to the BANK B common
account, which means this transfer will not credit the funds directly into
the customer’s A/c.

• In the process of BANK A initiating and transferring funds to BANK B

common account, there will be Scripts generated. These Scripts will
contain the manual download codes for the fund transfer.

• The Scripts generated from different steps of the transfer will be enclosed
in the transfer screenshots and will be downloadable at the Bank B by
the designated bank officers, by manually inputing the download codes
for each provided field.
 • The receiving bank officer will click on the SETTLEMENT button, which
will finalize the transfer process and will update the SENDER’S BANK
system with the FINISHED/FINALIZED status of the transfer.

• Banker/Bank officer of the destination bank (receiver bank) must then

operate and manually credit the beneficiary account from the bank’s
common account, which brings the word DOWNLOADING into play.

“BANK A” UPLOADS THE FUNDS TO THE COMMON ACCOUNT OF THE

“BANK B”. “BANK A” SENDS COPIES OF THE SCREEN SHOTS AND THE
SLIP OF FUNDS TRANSFER. IN OTHER WORDS, AFTER “BANK A”
DELIVERS THE FUNDS INTO THE “BANK B” COMMON ACCOUNT, THE
DOWNLOADING PROCESS AND CREDITING THE FUNDS TO THE
BENEFICIARY ACCOUNT IS THE “BANK B” SOLE RESPONSIBILITY.

• An important aspect of this type of funds transfer from the SENDER’S

BANK is that the SENDER’S BANK is capable of transferring CASH
/Order fund at present, rather than Cash Line, so the SENDER’S BANK
transferring the funds will be in the form of CASH, which implies that the
source of funds is CASH in origin.

• DOWNLOADING is the process in which the banker/officer of receiver’s

bank will see the arrived funds from the sender’s bank in the bank’s
common a/c and he/she will pass an entry and credit the beneficiary
account in a manual operation known to all bank officers.

• CLEARING the funds and distributing the shares of the entities involved
and mentioned in TRANSFER CONTRACT will take place in the
destination bank (receiver bank) and by the operation of the
corresponding bank officer.