Software Requirements
Specification
On
MiniCheck ID Pro™
Prepared by (TEAM #2)
Imran Ullah Mohammed
Anjali Satam
Megha Dubey
1
1. Introduction
1.1 Purpose:
Software Requirements Specifications provide
technical as well as the functional
details required for the project. The project deals with integrating the credit card
processing into the MiniCheck ID™ in order to enhance the architecture of the existing
project.
1.2 Definitions, Acronyms and Abbreviations
AIM – Advanced Integration Method
SSL – Secure Socket Layer
1.3 Intended Audience and Suggestions
This document is meant for Users, software Developers and testers
1.4 Project Scope
The entire application is designed by the MiniCheck OCR Inc, which developed a
software product called MiniCheck MGR and MiniCheck ID to scan, validate and
process checks and barcodes. The scope is to minimize the fraud transaction due to the
fake credit card by verifying and validating the credit card details, processing and
authorizing the credit card.
1.5 References
Authorize.Net
www.authorize.net
Project History and its Specification on the website given
http://dcm.cl.uh.edu/yue/courses/csci6838/Summer2008/
2
Software Requirements Specifications
http://www.techwr-l.com/techwhirl/magazine/writing/softwarerequirementspecs.html
2. Overall Description
2.1 Product Perspective
MiniCheck OCR , Inc has developed two applications MiniCheck MGR™ and MiniCheck
ID™ is used for processing checks and validating IDs at the point of sale where ID
Validation or age verification is required, in order to prevent losses due to fraud.
2.2 Product Features

When a Credit card is swiped through Card Reader or the Card Scanner, credit card
processing takes place, track 1 and track 2 data appears in the form of raw data.
The raw data consists of track 1 and track 2 data which consists of several details
o Credit Card Number
o Credit Card Expiration Dates
o Credit Card Holders First Name, Middle Name and Last Name
o Service Code
The above data appear in the form of raw data which is parsed into the useful data and
displayed on the user interface i.e. Window forms.
Credit Card Number, Credit Card Expiration Date and Credit Card Holders First Name,
Middle Name and Last Name.

The above details are transmitted in the encoded format to the payment Gateway
through AIM
o Track1 data OR Track2 data OR credit card number and card Expiration
date
o x_login : API login ID for the Payment gateway account
3
o x_tran_key: The transaction key is used by the system to authenticate
requests.
o x_markest_type : Market type that is configured for your account(For
Retail, it is 2)
o x_device type: The device type that is configured for your account. The
value can vary from 1 to 10.
o x_cpversion: Version 1.0 is currently the only supported version.
o x_response_format: Determines the format of the system response to a
transaction request.

The payment gateway will authorize the credit card and once the transaction is
approved, the merchant can print a receipt for obtaining the cardholder’s signature. But
if the transaction fails, it sends a corresponding error code and an appropriate status
message is displayed to the user.
Payment Gateway

The main requirement is to implement the credit card processing into the existing
MiniCheck ID™ software. MiniCheck ID Pro™ will be combined with the payment
gateway like Authorize.Net which will allow merchants to process credit card
transactions manually from any PC with internet access using a USB enabled
magnetic stripe reader.

Payment Gateway acts as a bridge between a merchant’s point of purchase and
the financial institutions where the payment transaction will take place.
The payment is transmitted to the Authorize.Net using Advanced Integration
Method (AIM).
For Implementing AIM, following requirements must be fulfilled
o Have a Secure Socket Layer (SSL) digital certificate
o Provide Server and Client side encryption
o Developing of a script on a web server for the integration to the gateway.

Payment Gateway will process the credit card transactions and help to identify
the Fraud transactions made with the help of Card Present 1.0 API.
4
2.3 Additional Requirements

Merchant will be provided with the Payment gateway login and password so the
user can avoid re-entering the information in the configuration screen.

Functionalities will be added for generating the marketing lists using several
search options and to set up user-defined product ID names or codes found in
the MiniCheck MGR™ software application.

Under create List option, the mailing list labels format option will be expanded to
include more choices of label format.
2.4 Operating Environment

Windows Operating System
2.5 Design and Implementation Constraints
Effort will be taken to mask the identity of outside vendors and to promote the Minicheck
brand Identity.
2.6 Dependencies
The project will use the Payment Gateway i.e. Authorize .Net to authorize and process
the credit the credit card which will accept or decline the transactions. Thus the
application depends on the Payment gateway to process the credit card.
3. External interface Requirements
3.1 User Interfaces
The project will use the Windows form to display the credit card information.
5
3.2 Hardware Interface
User will use several devices

MiniSwipe

Card Scan

MICR

Excella STX

MagnePrint scanners
3.3 Software Interfaces

Microsoft Visual Source Safe

Microsoft .Net 2.0 Framework and C#

MS-Access

Microsoft Visual Studio 2005

Microsoft Visio 2003

Atalasoft (DotImage 6.0)

PC Guard for .Net
3.4 Communication Interface
User must host their own secure payment form and send transaction to the payment
gateway using an end to end Secure Socket layer connection as a communication
protocol.
6