Pre-paid Recharging System on Banking.
Pre-paid Recharging System on Banking.
ABSTRACT
Pre-paid Recharging System aims to customize the existing pre-paid system offered by a pre-paid card Agent to the requirements of a Bank, say, ICICI and a Service provider, say, Airtel and integrate it in their existing enterprise system. The system will become the base system and foundation of complete wireless commerce framework. The primary audience is the bank and service providers. Ultimately, all members of the Project Team are the intended audience. The product must be a web-based and work as stand-alone product.
In practical, our project makes a customer not to venture outside anywhere from his sitting room for recharging the mobile, that is, from his seat itself, he can able to perform recharge applications through a single message. This facility is what we are providing through our project. The product must be platform independent and it must use link to its home page. This software would satisfy the needs of the clients such, by its security aspects and necessary controls that are adopted by the Programmer and save the messages that has been sent over.
Architecture
The given diagram is the basic diagram of our project. It represents the components of our project. It briefly tells the modules of our project
In short, a customer (client mobile) will contact the dealer regarding Recharging the SIM .Then, the dealer will make contacts with the bank and service provider for making the cell recharged. This will be the overview of our project.
Project Architecture
For doing this job, we need three servers, namely;
Agent Server – makes connections between bank,service provider and client
Bank Server – Banks
Service Provider – Mobile Service Provider
2.2 EXISTING SYSTEM
In the modern world, cell phones have been used by majority of the people around the world. The normal procedure for cell phone activation Pre paid system takes on with;
1. Buying the SIM card from the dealer
2. Scratch the card.
3. Type the 13 digit number
4. After these procedures only, prepaid system exists in a cell phone.
This is what happens in the existing system. This is not at all a problem for the customers, but, in the fast moving world, every one is working like a machine. So, for making their work to move in a smooth manner without tension and for saving their precious time, we are introducing a system called SMS TOPUP system.
2.3 PROPOSED SYSTEM
In the proposed system, the customers have to make a SMS for recharging the SIM card. The SMS contains the details of
1. Mobile Number.
2. Account Number.
3. PIN Number.
4. Amount for which the recharge is to be done.
After SMS has been sent to the dealer, he make contacts with the specified service provider and specified bank and finishes the job.
The Modules of our Project are,
• User Interface
1. Mobile GUI.
2. Agent Server GUI.
3. Service Provider Server GUI.
• Transactional components.
1. Agent Component
a) Registration.
b) Validity.
c) Transaction.
2. Bank Component
a) Registration.
b) Validity.
c) Transaction.
3. Service Provider Component
a) Registration.
b) Validity.
c) Transaction.
• Web Components
1. Agent Admin Control Panel.
2. Bank Admin Control Panel.
3. Service Provider Admin Control Panel.
• USER INTERFACE:
The module is named as User interface because it is fully designed for the purpose of each and every user working for recharging the sim card. This job makes user friendlier with the computer, cell phones, etc. This module is developed using Java 2 Standard Edition, which is simply called as J2SE.
The User Interface module is developed with three sub contents, namely;
I. Mobile GUI:
The client is provided with a GUI to interact with the Server
The mobile phone operations to be carried out by the client has been designed with forms and these forms are designed using Java
MIDlet packages which includes,
javax.microedition.midlet.
javax.microedition.lcdui.
javax.microedition.io.
This interface consists of five sections, namely;
1. Recharge:
The Recharge section is used by the user for entering the mobile number, Bank Account PIN number and the amount for which he wants to recharge the SIM card.
2. Customer Care:
On completion of each transaction, the client is provided with a Transaction ID, which he can use to check the status of the transactions made by him. With this, the users can clear their doubts and other queries.
This is called as Customer Care services.
3. Balance:
Balance section is also used by the client for viewing the balance
made in their transactions.
4. Help:
Help section gives the details for how to make use of this interface.
II. Agent Server GUI:
The Agent Server User Interface has been developed using J2SE.
This server is used by the agent, who makes connection between service provider, bank and client. This server is used for
1. Starting the Server.
2. Stopping the Server.
3. Viewing Transactions with the needed details.
III. Bank Server GUI:
The Bank Server User Interface has also been developed using J2SE. This server is used by the bankers , who have been dealing transactions with both service provider and client. This server is used for
1. Starting the Server.
2. Stopping the Server.
3. Viewing Bank Transactions with the needed details.
• TRANSACTION COMPONENTS:
First of all, components are manageable and discrete chunk
of logic. Transaction details are useful for the transactions that have been carried out by the client, bank and service provider for recharging the sim card. This module has been developed using the J2EE Technology. The components of this transaction are;
I. Agent Components:
This component manages the transactions that are likely to be carried out by the agent. This comprises of the following sections,
1. Registration:
Registration section deals with the registration of the persons, who have bought the SIM from the Agent
2. Validity:
Validity section deals with the validation of the client, which clears that whether the client is a registered user or not.
3. Transaction:
After the Client has been considered as a registered and validated user, he/she is eligible for making furthermore transaction. This is explained in the transaction section.
II. Bank Components:
This component manages the transactions that are likely to be carried out by the bank. This comprises of the following sections,
1. Registration:
Registration section deals with the registration of the clients for
creating a new Account. A client can utilize this software, if he/she is having the account in the recognized bank. If he/she is not a registered user, then he/she is not capable of making any transactions.
2. Validity:
Validity section deals with the validation of the client, which clears that whether the client is a registered user or not by checking whether the given PIN(Personal Identification Number) is valid or not.
3. Transaction:
After the Client has been considered as a registered and validated user, he/she is eligible for making furthermore transaction. This is explained in the transaction section.
III. Service Provider Components:
This component manages the transactions that are likely to be carried out by the service provider. This comprises of the following sections,
1. Registration:
Registration section deals with the registration of the clients who are all using the service provider’s services. A client can utilize this software, if he/she is provided with the service of the particular service provider. If he/she is not a registered user, then he/she is not capable of making any transactions.
2. Validity:
Validity section deals with the validation of the client, which clears that whether the client is a registered user or not by checking whether the given Mobile number is a valid service provider number or not.
3. Transaction:
After the Client has been considered as a registered and validated user, he/she is eligible for making furthermore transaction. This is explained in the transaction section.
SOFTWARE REQUIREMENT:
Operating System : Windows 95/98/2000/NT4.0.
Mobile Technology : J2ME
Front End : Java (Swing)
Database Connectivity : JDBC.
Comments are closed.