Академический Документы
Профессиональный Документы
Культура Документы
A PROJECT REPORT
Submitted by
VADIVELU.B
(Registration Number: 41406621052)
Of
June 2009
BONAFIDE CERTIFICATE
Certified that this project report titled “CARD SECURE PURCHASE ALERT” is the
out the research under my supervision. Certified further, that to the best of my knowledge
the work reported herein does not form part of any other project report or dissertation on
the basis of which a degree or award was conferred on an earlier occasion on this or any
other candidate.
The Card Secure Purchase Alert is a real-time fraud mitigation and 2 way
communication alert platform embedded in the payment stream resulting in quick
response, no false positives, and no disruption to the payment process.
Using secure web and mobile based technology, Purchase Alert can identify a
fraudulent payment transaction within seconds and put the consumer in immediate
contact with the consumer’s bank either through an instantly generated text message,
email or telephone call allowing the consumer to instantly respond and communicate with
the bank.
Effective and affordable fraud detection tool that reduces time and costs of fraud
mitigation, Customization and flexibility that incorporates your organization's baseline
rules to align with policy and safeguards Multi-channel functionality that meets the
diverse channel preferences of your accountholders-be it mobile, PDA, email, land line,
etc.
ACKNOWLEDGEMENT
With profound indebtedness I thank Mr. Vikrama cholan M.C.A, Anju soft(india)
private limited chennai for her constant encouragement and expert guidance throughout
the project.
I express my thanks to all my department faculty members and technical staff members
for providing necessary information and their sustained interest in my part of fruitful
completion
Last but not the least, I put my sincere thanks to My Parents and Friends who helped
me in the course of my project.
CONTENTS
3.5.1 LOGIN 26
3.5.2 MY PROFILE
3.5.4 TRANSACTION
3.5.5 RULE
3.5.6 MERCHANT
LIST OF FIGURES
FIGURE NO TITLE
PAGE NO
3.3.4 ER DIAGRAM 20
6.1.5 TRANSACTION 44
LIST OF ABBREVATIONS
The Card Secure Purchase Alert is a real-time fraud mitigation and 2 way
response, no false positives, and no disruption to the payment process. Using secure web
transaction within seconds and put the consumer in immediate contact with the
consumer’s bank either through an instantly generated text message, email or telephone
call allowing the consumer to instantly respond and communicate with the bank.
CHAPTER 2
SYSTEM ANALYSIS
2.1.1 Drawbacks
The consumer has no way to control the purchasing power.
The existing system has no solution for reduce the time and expense of fraud
mitigation.
There is no financial security with a single source to monitor all accounts.
There is no actionable alerts sent to consumer based on individual preferences
2.2 Proposed system
Card secure consumers can take control of their financial identity and
purchasing power. Card Secure provides consumers with an additional level of security
and peace of mind during the payment experience and can help reduce resolution time
and frustrations associated with resolving payment fraud. This system is developed to
identify a fraudulent payment transaction within seconds and put the consumer in
immediate contact through text message email or telephone call.
The Technical feasibility study determines whether the desired project should
be done with the current equipment or with the new technology if required. In my project
the all forms are very easy to access and update the all information. There is no complex
to retrieve the user data. The system is provided with the necessary features to maintain
accuracy, reliability and data security. Hence the proposed system was found to be
technically feasible.
. NET FRAMEWORK
The .NET Framework is an integral Windows component that supports building
and running the next generation of applications and XML Web services. The .NET
Framework is designed to fulfill the following objectives:
Advantages:
Features:
• There are no global variables or functions. All methods and members must be
declared within classes. It is possible, however, to use static methods/variables
within public classes instead of global variables/functions.
• C# supports a strict Boolean data type, bool. Statements that take conditions,
such as while and if require an expression of a Boolean type.
• Managed memory cannot be explicitly freed, but is automatically garbage
collected. Garbage collection addresses memory leaks.
• C# is more type safe than C++. The only implicit conversions by default are
those, which are considered safe, such as widening of integers and conversion
from a derived type to a base type. This is enforced at compile-time, during JIT,
and, in some cases, at runtime. There are no implicit conversions between
Booleans and integers, nor between enumeration members and integers. Any user-
defined conversion must be explicitly marked as explicit or implicit, unlike C++
copy constructors and conversion operators, which are both, implicit by default.
• C# currently (as of 3 June 2008) has 77 reserved words.
MICROSOFT SQL SERVER 2005:
SQL Server 2005 offers new features and enhancements that improve productivity,
efficiency, availability, and administrative ease.
Database mirroring
The primary database continuously sends transaction logs to the backup database on a
separate SQL Server instance. A third SQL Server instance is then used as a witness
database to monitor the interaction between the primary and the mirror databases.
Database snapshots
A database snapshot is essentially an instant read-only copy of a database. In
addition to being a great reporting tool, users can revert control from primary database to
a snapshot database in the event of an error
CLR integration
With SQL Server 2005, users now have the ability to create custom .NET objects
with the database engine. For example, stored procedures, triggers, and functions can
now be created using familiar .NET languages such as VB and C#.
Service Broker
DDL triggers
DDL triggers are defined at the server or database level and fire when DDL
statements occur. This gives the ability to audit when new tables, stored procedures, or
logins are created.
Ranking functions
SQL Server 2005 provides the ability to rank result sets returned from the
database engine. This allows to customize the manner in which result sets are returned,
such as creating customized paging functions for Web site data.
XML integration
SQL Server 2005 introduces the new XML data-type. This allows users to store
full XML documents in this new data-type, and you can place validations on the well-
formed documents in the database
Database Mail
Database Mail uses standard SMTP to send e-mail messages. These messages
may contain query results, attachments (which can be governed by the DBA), and is fully
cluster aware.
5. PROJECT DESCRIPTION
5.1 PROBLEM DEFINTION
institutions, card companies and processors- can now deploy a real-time fraud mitigation
and 2-way communication alert platform that is embedded in the payment stream. This
innovative solution enables you to detect fraud in real time while engaging in 2-way
additional level of security and peace of mind to the consumer payment experience and
enables consumers to take control of their financial identity and purchasing power.
Using secure web and mobile-based technology, Purchase Alert can identify a fraudulent
A Typical Transaction:
Card Secure takes immediate action and stops future fraudulent transactions
alerts of account activity, enabling them to instantly validate payment activity on their
accounts. Card Secure Purchase Alert delivers fraud alerts based on your accountholder’s
individual preferences—text message, mobile phone, email, landline, email, etc. card
secure works in parallel with the payment process—providing a convenient way to add
Development process
The development process starts with the analysis phase where necessary requirement
are gathered, sequence diagrams are generated in the design phase, coding is done in .Net
Framework, testing the model, integrating the model, fixing the bugs if any and
implementing the model.
The following basic input devices are used in my project for the system to accept input
from the user
1. Keyboard
2. Mouse
SSO uses various controls that allow users to furnish information as input to the
system. Some of those input controls are mentioned below:
1. Text Box
2. Drop Down List box
3. Radio Button List
4. Check Box List
5.5 OUTPUT DESIGN
Output is the primary purpose of any system. Output design is often discussed
before other aspects of design because, from the client's point of view, the output is the
system. Output is what the client is buying when he or she pays for a development
project. Inputs, databases, and processes exist to provide output.
Coding the program for each module with its logic is performed in this step.
Proper software specifications are also done here.
Computer output is the most important and direct source of information to user.
Output design is a process that involves designing necessary outputs that have to be
various users according to their requirements. Efficient intelligent output design should
improve the system relationship with the user and help in decision making.
The output data design is made in such a way that it is easily understandable to
the data entry operators by using meaningful and appropriate messages. When designing
output, a system analyst accomplishes the following.
designing database file, which are the key source of information to the system.
many users quickly and effectively. The general objective is to make information access
The databases are implemented using a DBMS package. Each particular DBMS has
The proposed system CARD SECURE stores the information relevant for processing
in the MS SQL SERVER Database. MS SQL SERVER database contain tables, where
each table corresponds to one particular type of Information. Each piece of information in
A table also contains records, which is a set of fields. All records in a table have the
same set of fields with different information. Each row in a table is said to be entity. Each
Each table contains key fields that establish relationship in a MS SQL SERVER
database and how the records are stored. There are primary key fields that uniquely
identify a record in a table. The tables consist of more than one n Normalization process.
NORMALIZATION
The term normalization of data refers to the way data items are grouped together into the
• Repetition of data
• Loss of information
• Inconsistency
All the tables have been normalized up to the second normal form. Various narmal forms
A relation is said to be in 1NF (First Normal Form) if the values in the domain of each
attribute of the relation are automatic, i.e., only one value is associated with each attribute
and the value is not a set of values. A database is said to be in 1NF if all the relations of
The 2NF is based on the concept of full functional dependence. A relation is said to be
in 2NF (Second Normal Form) if and only if it is in 1NF and every non-key attribute is
The 3NF is based on the concept of transitive dependency. A relation in 2NF if and
Table Name:Card_Master
Rule nVarchar(max)
TableName:FI_master
Fieldname Datatype Lenght Constraints
S_no int 4
Tran_id int 20
Tran_date datetime
Reply_received bit
Status char
Level 0
This level shows the overall context of the system and its operating
environment and shows the whole system as just one process
Level 1
The purpose of this level is to show the major high level processes of the system
and their interrelation
Level 2
This level is a decomposition of a process shown in a level 1 diagram, as such
there should be a level 2 diagrams for each and every process shown in a level 1 diagram
DFD LEVEL 0
Consumer Registe
Authenti
Global unique cation
Identifier (GUID)
Card no
Level-2
Transaction
Merchant
Transaction details Swipes FITS
details
Transaction
FIS Verification
Execute rules
Reply
Consumer SMS/Email
Rules
/verification
5.8 Entity Relationship Diagram
ExpYea
Cardtyp r ExpMo
e n
Userid Card id
Pwd FIName
Register
Card Master
User
have
Rule master
Sms Card_n
op
Email Rule
CHAPTER 6
SYSTEM TESTING
System testing is the stage of implementations, which is aimed at ensuring that the
system works accurately and efficiently before live operation commences. A series of
testing is done for proposed system before the system is ready for user acceptance. Test
data are prepared and the system is tested using the test data. System testing is a critical
element of software quality assurance and represents the ultimate review of specification,
design and coding. Testing objective should be to design the tests that systematically
uncover different classes of errors and do so with minimum amount of time and effort.
The tests are made functional, structural and simple.
Testing Objective
The objectives of the testing are:
Testing is a process of executing a program with the intent finding
an error.
A good test case is one that has high probability of finding an as
yet undiscovered error.
Types of Testing
Unit Testing
Integration Testing
Validation Testing
Performance Testing
UNIT TESTING
Each module interface is tested to ensure that information properly flows in to and
out of the program unit under test. As the system is getting up the development ladder, it
is tested unit by unit. All common errors of computation are uncovered in this testing
method.
INTEGRATION TESTING
Integration Testing is a logical extension of unit testing. In this simplest form, two
units that have already been tested are combined into a component and the interface
between them is tested. Integration testing is done is three ways, they are:
Top down approach
Bottom up approach
The top-down approach to integration testing requires the highest-level modules
be tested and integrated first. The bottom-up approach requires the lowest-level units be
tested and integrated first. First, the inputs for functions are integrated in the bottom-up
pattern discussed above. The outputs for each function are then integrated in the top-
down manner.
VALIDATION TESTING:
Validation can be defined in many ways, but a simple definition is that can be
reasonable expected by the customer, which is defined in the software requirement
specification, a document that describes all user visible attribute of the software.
The following test producers are followed during system development:
Testing each option independently
Testing all possible combinations of image file formats entered by user including
invalid data
The users of the company are trained to operate the developed system. Both the
hardware and software are made to run the developed system successfully in the future.
Test Cases
During the design phase, the product structure, its undergoing data structure,
the general algorithm and the interfaces a control/data linkage needed to support
communication among the various substructures was established.
Implementation is the final and important phase. The most critical stage in
achieving a successful new system and in giving the users a confidence that the new
system will work and be effective is that the system can be implemented only after
thorough testing is done and if it found to working according to the specification.
internet and user can access any time. Easy to access and secure the credit/debit cards in
8.1 CONCLUSION
I feel happy and proud in making my project “CARD SECURE PURCHASE
programming. This training improved to ability to develop flexible solutions to the given
project.
Programs have been developed and implemented as per the requirements of the
users. This system is user-friendly and hence very easy to operate. In all these
applications, the company can get the satisfied output. Hence the company can drive the
Apart from the programming, I also came to know about the various tools need for
Finally, I am proud in doing project and also I conclude this project “CARD
}
protected void LinkButton1_Click(object sender, EventArgs e)
{
Response.Redirect("Signup.aspx");
}
protected void LinkButton4_Click(object sender, EventArgs e)
{
Response.Redirect("Cardsec_consumer.aspx");
}
protected void LinkButton5_Click(object sender, EventArgs e)
{
Response.Redirect("Cardsec_consumer.aspx");
}
protected void LinkButton3_Click(object sender, EventArgs e)
{
string q = "select * from Master_Profile where Login ='" +
TextBox1.Text + "' ";
db.dt.Rows.Clear();
db.dt.Columns.Clear();
db.getdata(q);
if (db.dt.Rows.Count != 0)
{
Session["login_name"] = TextBox1.Text;
Response.Redirect("Forgot_Password.aspx");
}
else
{
Lblaccmsg.Visible = true;
Lblaccmsg.Text = "Enter the valid user name";
}
protected void Button1_Click(object sender, EventArgs e)
{
}
else
{
Lblaccmsg.Visible = true;
Lblaccmsg.Text = "You are not a valid user";
}
}
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
string s = "select
CardID,Nick_Name,substring(Card_No,13,4) as CardNo,Amount,Expiry_Date
from Card_Details where user_name='" + Label3.Text + "'";
db.dt.Rows.Clear();
db.dt.Columns.Clear();
db.Bind(s);
datagrid1.DataSource = db.ds;
datagrid1.DataBind();
}
}
}
}
protected void Button1_Click(object sender, EventArgs e)
{
string aa = "null";
Label8.Visible =false;
string loginname = Session["username"].ToString();
Label3.Text = loginname.ToString();
if (Btnaddcart.Text == "Submit")
{
if (Txtnickname.Text != "" && Textamount.Text !="" &&
TxtExpirydate.Text !="" && Txtcardno.Text !="")
{
int dd=Txtcardno.Text.Length;
if (dd == 16)
{
}
else
{
Label8.Visible = true;
Label8.Text = "Enter all the Fields";
}
}
else if (Btnaddcart.Text == "Update")
{
db.dt.Rows.Clear();
db.dt.Columns.Clear();
db.Bind(sbind);
datagrid1.DataSource = db.ds;
datagrid1.DataBind();
Btnaddcart.Text = "Submit";
}
protected void Txtcardno_TextChanged(object sender, EventArgs e)
{
}
protected void datagrid1_ItemCommand(object source,
DataGridCommandEventArgs e)
{
Label1.Visible = false;
Btnaddcart.Text = "Update";
int l;
string code;
l = e.Item.ItemIndex;
code = e.Item.Cells[0].Text.ToString();
Session["card_id"] = code.ToString();
string loginname = Session["username"].ToString();
Label2.Text = loginname.ToString();
string squery1 = "select
Financial_inst_name,Card_type,Nick_Name,substring(Card_No,13,4) as
CardNo,Amount,Expiry_Date from Card_Details where CardID='" +
code.Trim() + "' and user_name='" + Label2.Text + "'";
db.dt.Rows.Clear();
db.dt.Columns.Clear();
db.getdata(squery1);
if (db.dt.Rows.Count != 0)
{
Dropfinancialinst.SelectedItem.Text =
db.dt.Rows[0]["Financial_inst_name"].ToString();
DropCardtype1.SelectedItem.Text =
db.dt.Rows[0]["Card_type"].ToString();
Txtnickname.Text = db.dt.Rows[0]["Nick_Name"].ToString();
Txtcardno.Text = db.dt.Rows[0]["Card_No"].ToString();
Textamount.Text = db.dt.Rows[0]["Amount"].ToString();
TxtExpirydate.Text = db.dt.Rows[0]["Expiry_Date"].ToString();
}
else
{
Label1.Visible = true;
Label1.Text = "Debit/Credit details is not available ";
}
}
protected void datagrid1_DeleteCommand(object source,
DataGridCommandEventArgs e)
{
Label1.Visible = false;
int l;
string code;
l = e.Item.ItemIndex;
code = e.Item.Cells[0].Text.ToString();
string sdelete = "delete from Card_Details where CardID='" +
code.Trim() + "' and user_name='" + Label2.Text + "'";
db.delete(sdelete);
Label1.Visible = true;
Label1.Text = "Card Details is deleted successfully";
string sbind = "select * from Card_Details where user_name='" +
Label2.Text + "'";
db.dt.Rows.Clear();
db.dt.Columns.Clear();
db.Bind(sbind);
datagrid1.DataSource = db.ds;
datagrid1.DataBind();
Btnaddcart.Text = "Submit";
}
protected void DropCardtype1_SelectedIndexChanged(object sender,
EventArgs e)
{
}
}
CHAPTER 10
REFERENCES
BIBLIOGRAPHY
5. Reference Websites:
i.www.asp.net
ii.www.codeproject.com
iii.www.w3schools.com