Search This Blog

Wednesday 20 July 2011

E-Transaction



The E-Transaction Interface is the designed targeted at the future banking solution for the users who is having multiple bank accounts at the multiple banks. This interface integrates all existing banks and provides business solutions for both retail and corporate.
          This system acts as a standard interface between the clients and all the banks that register with the system and clients who maintains accounts in various banks don’t have to visit individual bank’s website to make money transactions instead he can directly log on to E-Transaction Interface and make any kind of request and get his work fulfilled and in the backend the system will take care of all the obligation required in order to carry on transaction smoothly
                          The main Vision of this project is to eliminate all the diversities amongst banks, which generally client faces at the time of any transaction. By doing so Client will used to only one Systematic Standard way of banking and there by they will be at ease using this interface.
              The kind of functionality it’s capable of providing also reveals the kind of banking facilities that a customer could get online. Of course, the bank that implements this solution decides the features available to customers.                     









Modules

1) Banker Module
This module deals with the Accounts Pending, Pending Transfers, and Reports regarding transactions.

2) Customer Module
This module a customer can register him self to the system, customer can login into the system. A customer can add a new account, view the account information, Transfer amount, A customer can also see the Transaction Reports.

3) Admin Module
The admin module will be used by the administrator of the site, The admin can accept or reject the request from the banker, and The admin can accept or reject the request from the user. The request are in the form of bank registration, customer registration.

Existing System:

Lets consider a condition when a bank customer is having bank accounts in more than one bank. The online banking system available at present is bank specific. Each bank is having its own interface to interact with the bank. A customer can login to the bank and make the transactions using the online banking provided by the bank. The way he interacts with different banks varies. The user must learn how to interact with each system.

DRAWBACKS OF EXISTING SYSTEM
A user requires accessing the system on the fly. The user interfaces designed by the different banks will confuse the user. He requires to learn how to use each and every user interface of the bank in which he is having accounts. This process may be time consuming and too irritating for the user also. When he transfers the accounts, He may probably prone to click the different action when shifting from one bank user interface to other.
Proposed System and its features:
The e-Transaction Interface provides the following system features.
1.      This system provides a Common User Interface for the customers to log on to any bank.
2.      Here the user interface is Graphical User Interface.
3.      This application is a Web based Application.
4.      Being a web based application it doesn’t require any client side installation.
5.      Any number of users can interact with the system simultaneously.
6.      Eradicates the time consumed to learn how to use all the user interfaces of every bank in which a customer is having account.
The transactions are secure
Number of Modules:
1) Admin Module
Only an Administrator can have access to this module, He must accept or reject the Banker who registered with the system. He performs the counter check on the banker who applied for registration with the system. He must also authorize the pending user requests also. If a user or banker registers with the system the administrator must authorize the user or banker to register with the system. Finally it calls the sign out button, which will take the administrator to the home page. The module will update the database after the administrator has authorized or declined the user requests.
2) Banker Module
Through this module the banker can accept the request for registering the account of a user with the system. And a banker can accept or decline any transaction from the user. If a user requires to transfer some amount to any other account. The user request was first sent to the banker. The banker verifies the request and then accepts or declines the transaction. If he accepts the transaction then the transfer of funds starts. If he clicks on decline then the request was rejected and notified to the user. In this module some special care should be taken after the baker accepts the request. The transaction must be obeying the ACID properties. All the commands in the transaction must be executed successfully else the entire process must be rolled back.
3) Customer Module
To become a customer to the system. The person must register with the system first. By clicking on the sign in a person can have access to the application form, which consists of the details about the person. Then the request is sent to the administrator. After the administrator accepted the request from the customer, The customer can login to this account. Then after logging in with the user name and password given by the administrator. The system verifies the username and password with the database stored and then it gives the access to the customer login page. The customer login page consists of select account; create a new account, back and home page buttons. If a user requires to register a new bank account. He clicks the new account and fills the particulars and click on submit button. The request was sent to the specified bank admin for acceptance. After acceptance the user can use the bank account for the funds transfer. The funds transfer screen displays the current account balance in the bank and amount to be transferred and the target account to which the funds to be transferred. The request is sent to the banker for verification and acceptance. The funds are successfully transferred if the banker accepts. The customer can also see the pending transfers. The present status of the transfer from his login.


HARDWARE AND SOFTWARE REQUIREMENTS

HARDWARE REQUIREMENTS                              
PROCESSOR    :  Intel 2.0 GHz or above
HARD DISK     :  80 GB
RAM                 :    512 MB RAM.

   SOFTWARE REQUIREMENTS

OPERATING SYSTEM                     : WINDOWS XP with SP2. 
LANGUAGE (FRONT END)   : JAVA (JDK1.5/1.6)
SERVER                                     : APACHE TOMCAT 5.5/6.0
WEB TECHNOLOGY              : HTML, JAVASCRIPT, CSS.
DATABASE (BACK END)        : ORACLE 10G.
ARCHITECTURE                      : 3-TIER ARCHITECTURE.

No comments:

Post a Comment