Scribd
Upload
189 views3 pages

H2H ProcessFlow V1.1 New

Kotak Mahindra Bank offers host-to-host file transfer functionality using SFTP over port 22 for customers. It allows for encrypted file transfers from client to bank using a Java utility, and reverse encrypted transfers from bank to client using the same method. The process involves file encryption at the client, transfer to the bank server, decryption at the bank, potential processing, then reverse encryption and transfer of any response files back to the client for decryption.

Uploaded by

rakesh1619
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
189 views3 pages

H2H ProcessFlow V1.1 New

Kotak Mahindra Bank offers host-to-host file transfer functionality using SFTP over port 22 for customers. It allows for encrypted file transfers from client to bank using a Java utility, and reverse encrypted transfers from bank to client using the same method. The process involves file encryption at the client, transfer to the bank server, decryption at the bank, potential processing, then reverse encryption and transfer of any response files back to the client for decryption.

Uploaded by

rakesh1619
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Host to Host Process Flow

File Encryption at client File Decryption at Bank’s


end end

SFTP SFTP
Port 22 Port 22
Encrypted files transfer from Client to bank
Client Server Client Firewall Server Bank Firewall Bank Server

Encrypted Reverse files transfer from Bank


to Client Server

Reverse File Decryption at Reverse File Encryption at


Client’s end Bank’s end

H2H Functionality – Kotak Mahindra Bank Limited

Kotak Mahindra Bank Limited offers Host to Host functionality using FTP (PSFTP / PUTTY) with custom build
encryption facility via port 22 for the customers. It also has the capability to transmit the Reverse files back to
customer using the same platform.

Push Mechanism:

Encryption & File transfer will be handled by Java utility which will be deployed at client system.

Pull Mechanism:

Encryption if required will be handled by Java utility which will be deployed at client system. Customer will
have to provide access with necessary credentials (User name & password) to the bank for the location from
where the file needs to be picked.
Following process is followed for the Host to Host transfer of files for Push Mechanism.

File transfer (Client to Bank)

1) After the required port opening process is completed, the client will generate a raw file and park in one
designated folder.
2) The Java utility (provided by the bank) is executed which will pick the raw file from the designated
folder and encrypt the same and would push the encrypted file to the Kotak bank server through
Host2Host channel.
3) On receipt of the file at the Bank’s end an email will be triggered which will act as intimation to the
client for receipt of the file at Bank’s end.
4) The encrypted file received at Kotak bank end will be decrypted using the necessary certificates and
will then get processed.

Reverse File transfer (Bank to Client)

5) On the process completion, a reverse file will be generated which will then be transferred to the clients
end through the same H2H channel in encrypted mode…
6) The Java utility residing at the clients end will read the encrypted file and will decrypt the same.
7) This decrypted file is then uploaded back in the client system for necessary reconciliation.

Following process is followed for the Host to Host transfer of files for Pull Mechanism.

File transfer (Client to Bank)

1) After the required port opening process is completed, the client will generate a raw file and park in one
designated folder.
2) The Java utility (provided by the bank) is executed which will pick the raw file from the designated
folder and encrypt the same (If encryption is required).
3) Bank will then connect to the designated location with the credentials provided and will pull the files
for processing. On receipt of the file at the Bank’s end an email will be triggered which will act as
intimation to the client for receipt of the file at Bank’s end.
4) The encrypted file received at Kotak bank end will be decrypted using the necessary certificates and
will then get processed.

Reverse File transfer (Bank to Client)

5) On the process completion, a reverse file will be generated which will then be transferred to the clients
end through the same H2H channel in encrypted mode if required, else raw file will be transferred.
6) The Java utility residing at the clients end will read the encrypted file and will decrypt the same. If raw
file is transferred, the same will get processed as it is in the client system.
7) This decrypted file is then uploaded back in the client system for necessary reconciliation.
Sample Folder Structure (For H2H activity)

File transfer (Client to Bank)

D:\KOTAK\KOTAKFILETRANSFER\ (This folder will have all the necessary files for the H2H process)
D:\KOTAK\KOTAKFILETRANSFER\Input (This folder will contain the raw file generated from Clients end)
D:\KOTAK\KOTAKFILETRANSFER\Encrypted file (This folder will contain the file which is encrypted by
the Java utility provided by Bank)
The files generated will be processed basis the mechanism used.

Reverse File Transfer (Bank to Client)

D:\KOTAK\KOTAKFILETRANSFER\ReverseInput (This folder will contain the reverse file received from
Banks end)
D:\KOTAK\KOTAKFILETRANSFER\ReverseDecrypted (This folder will contain the reverse file which is
decrypted by the Java utility provided by Bank if encrypted file is received)

The decrypted file is then uploaded back in the client system for necessary reconciliation.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy