CREDIT CARD APPROVAL

SYSTEM
SUBMITTED BY:-
AKSHI
BHUTANI
DEEPIKA
NARANG
NIDHI YADAV
 INTRODUCTION

Introduction to Credit card

History of Credit card
Working of Credit card
Credit card numbering
 FEATURES OF CREDIT CARD

Logos
Number
Name
Expiry date
Magnetic strip
CVV Number
Signature
Contact Number
 TRANSACTION STEPS IN CREDIT
CARD

Authorization
Batching
Cleaning and settlement
Funding
Charge Backs
 ADVANTAGES OF CREDIT CARD

No immediate cash

Free credit
World wide usage
Tracking expense
E-buying Cash
 Withdrawal
 DISADVANTAGES OF CREDIT CARD

Interest cost 14%-15%person

Charge
Credit trap
Multiple card
 SECURITY PROBLEMS AND
SOLUTIONS

Over limit charges

Credit card fraud
Overview of real-time fraud detection and
prevention
 DIAGRAMATIC REPRESENTATION
OF CREDIT CARD SYSTEM

Flow chart for module ADMIN

Flow chart for module USER
DFD of Level-1(ADMIN AND USER MODULE)
DFD of Level-2(ADMIN AND USER MODULE)
Entity Relationship Diagram
 SYSTEM SPECIFICATION

Hardware requirement
 
Main Processor: Pentium IV
Hard-disk Capacity : 8 G.B
RAM: 256 MB
Clock Speed: 2.8 Hz
Floppy Drive: 1.44MB
Keyboard : 104 Key
Monitor: V.G.A
 SYSTEM SPECIFICATION (CNTD….)

Software Requirement
Operating System:
Windows 98, XP and above
 Language Used:
JAVA (j2sdk1.4.2_04)
Backend Used:
MS ACCESS
 SNAPSHOTS

Login
Credit card entry
Credit card approval
Credit card transaction
Register for security code
Credit card transaction
Transaction list
Change password
LOGIN
CREDIT CARD ETRY
CREDIT CARD APPROVAL
CREDIT CARD TRANSACTION
REGISTER FOR SECURITY CODE
CREDIT CARD TRANSACTION
TRANSACTION LIST
CHANGE PASSWORD
 TESTING OF CREDIT CARD
SYSTEM
Overview
Test scope
Test methodologies
Test schedule
 TEST OVERVIEW
Overview
Test plan objectives
Testing Assumptions
Risks & Contingencies
To ensure that the Credit card approval System will:
- Function consistently and reliably in accordance with
current business operations.
- Meet or exceed user requirements and technical
specifications.
- Not adversely impact other systems or the existing
technology environment
It is assumed that there are few reviewers and customers
whose personal details, username and password are
already stored in the database.
- The subscription codes of each customer are assumed
to be unique
The following risks apply to the testing process and may
impact either the comprehensive level of testing that can
be performed in each of the
Functional Units:
- The actual deployment of Article Information System
may take longer to perform than anticipated, as the
admin is also using the same
database for maintenance.
 TEST SCOPE
Test Scope

Features to be Tested All features, forms, reports and interfaces will be tested.
These include:
- Login forms
- Registration form

-Transaction

-Approval form

-Credit card security code

-Database used for both authentication and validation

Features Not to be Tested - Data integrity and system functionality contained within
the
Credit card Approval System and which is not Online
 TESTING METHODOLOGIES
Test Methodologies

Testing Approach The following approach will be used to test the

Credit card Approval
System
- System integration & system testing will be
conducted to provide an initial stable testing
environment as follows:
Integration Testing: Ensure operability of
System application within each of the new modules.
System Testing: Ensure that all the test
databases are accessible for testing.
- Test cases and associated scripts for user
acceptance testing are created.
- For testing the functional specification the unit
testing is performed
.
 TEST METHODOLOGIES (CNTD…)
Test Documents The following test documents will be created
and maintained throughout
the project lifecycle:
- System Test Plan
- Master test case lists for each of the
following functional units:
Login,
Add,Save,Approval,Transaction,Security
code, Search
- Test case scripts for each test case recorded
in the master test case list
- Log of all problems encountered during the
testing phase of the project
 TEST METHODOLOGIES (CNTD…)
Test Case Pass/Fail Each Test Case will be evaluated against the
Criteria acceptance criteria as outlined in the test case
scripts to determine if the test passed or
failed. In the case of a failure, the tester will
assign a severity to the problem using the
appropriate priority rating system established
within Tracker for each application.

Suspension/Resumption Test Cases that do not run to completion will

Criteria be evaluated on a case by case basis to
determine if the testing must start over or
resume at the point where the failure
occurred. In extremely long test cases,
checkpoints will
be established for resumption in the middle of
a test case where appropriate. In general, a
test may be resumed in the middle when the
error is not critical.
 TEST METHODOLOGIES (CNTD…)

Problem Errors identified through testing will be

Logging/Resolution logged. Resolve the problem According
to the deemed severity level, and update
the master test case list. Once the
problem has been fixed, record the
resolution into the database The failed
test case will then be retested using the
same test case script that detected the
error in order to verify that the problem
has been rectified.
 CONCLUSION

Using the credit card number, you submit an electronic request to the processing
network for "authorization to capture funds" from the cardholder's credit card
account in the amount of the purchase. Traditionally, one would submit this
request by swiping a credit card through an electronic transaction terminal
provided by the bank.
 With the system, this request is provided electronically to our payment gateway
servers, which then route the request along the processing network. Other
variations of verification systems are used by ecommerce merchants to determine
if the user's account is valid and able to accept the charge.
 These will typically involve the cardholder providing additional information,
such as the security code printed on the back of the card, or the address of the
cardholder.
 FUTURE WORK

It is expected that credit cards will gradually give way to smart cards. A smart
card has a microprocessor built into the card itself .Cryptography is essential to
the functioning of these cards in several ways; the user must corroborate with his
identity to the card each time a transaction is made, in much the same way that a
PIN is used with an ATM.
The enhanced memory and processing capacity of the smart card is many times
that of traditional magnetic strip card and can accommodate several different
applications on a single card.
Many parts of the world already use them, but their reach is limited. The smart
card will eventually be available to any one who wants one, but for now, it’s
available mostly to those participating in special programs.