Objective:
Create a system that will be able to produce replicated consumer credit portals rapidly (examples: americanoctane.com and commandmentcard.com), accept and process consumer credit applications, track user interactions and transactions, export user data, provide reporting, email transactional messages, and give consumers ability to shop using consumer line of credit.

Requirements:
- All transactions must be PCI compliant.
- User data will be validated using 3rd party service.
- User will have the ability to have multiple cards and/or accounts (UCL account name/login should be the credit number given to user)
- User will be able to use credit line to shop across all storefronts
- User will be required to make a down-payment for each item purchased (down payment % will be set per item) plus all shipping and handling fees using a valid debit or credit card, the rest of the purchase price will be made from their consumer credit line .
- User will be able to make payments towards credit line online.
- User can mail payments to processing center, customer service agent will then process the payment and credit the account.
- User will be able to cancel account/credit line online. No new charges can be made, but any outstanding payments will still be due.

Additional Requirements:
Requirements:
1 - Sign-up Process and billing:
1a - Ability to set price per sign-up (i.e. activation fee. Currently $99.00)
1b - Ability to set monthly maintenence fee (currently $9.95 charged to their line of credit).
1c - Ability to set annual price per add-on child (currently $5.00)
1d - Full transaction history will be available within the account.
1e - All credit card transactions must be PCI compliant (we work with Authorize.net as our merchant)
2 - Email management.
2a - Transactional emails (Account created, account renewed, account cancelled, new child added, new guardian added, etc).
4 - Information Back Ups. Along with redundant back-ups from our host, we'd like to schedule full data back-ups for the following:
4a - Individual account history, viewable by employees and management only. All transactions and interactions stored in a history under each customer.
4b - System wide back-ups. Build a daily back-up of the database and all web files and have them stored on a remote FTP server.
5 - Help Ticket System: Provide users the ability to communicate with customer service through their account by utilizing a help-ticket system. This can be an existing open source solution, provided it can be used securely within the user's account and not allow confidential data outside of the main system.
6 - UCL:
1 - Customer Service Representitive
A - Ability to add or disable user (customer) accounts (but not delete).
B - Ability to add or edit user data (changes will be logged, and user can revert if needed).
C - Ability to view and respond to help tickets.
D - Ability to charge users for membership fees, change credit card information, or refund to card.
2 - Managers
A - All the abilities of the CSR, plus:
B - Ability to add, disable CSR accounts
3 - Administrators
A - All the abilities of a Manager, plus:
B - Ability to add, disable Managers
C - Ability to add, disable Administrators
7 - CMS:
We'd like the ability to post articles, news/press releases, and blog posts. This can be done with a SIMPLE third party solution such as Wordpress, but the theme must be the same template as the rest of the site and tie into the navigation.
8 - Reports (preset time frames for reporting: Today, Yesterday, This week, Last Week, Month To Date, Last Month, This Quarter, Last Quarter, Year To Date, Each Year, Total Lifetime, and user select start and end dates for report)
A - Membership activity:
1 - Count all new accounts and sign-up revenue
2 - Count all revenues from shopping cart
3 - Count all revenues from payments, shopping cart, and sign-up
4 - Count all cancellations
5 - Count total child records
6 - Count all acc