Hell's Kitchen Systems, Inc.
HKS is now shipping version 3.2 of CCVS (Credit Card Verification System) and has hundreds of customer sites that include stand-alone merchants, merchant hosts, merchant-application integrators and merchant-application service providers. HKS's goal is to embed an electronic payment processor on every computer.
CCVS uses a computer to perform the same function as a credit-card swipe box found in most retail stores. Acting independently or as a component of a larger system, CCVS can process multiple payment types (credit card, ACH, EFT) in either real time or batch mode.
The system can be used within an electronic storefront on the Internet, or it can help run a mail-order business with custom-built applications for telephone operators.
CCVS can be used within the United States or Canada. It can also be used in other countries with credit-card clearing institutions that support any one of the CCVS-supported protocols.
Currently, CCVS works with either a modem or a leased line to communicate with the same credit-card clearinghouses used by traditional credit-card processing. (HKS plans to support other means of directly contacting clearinghouses, such as TCP/IP.) This approach has a few benefits. There's no need to worry about Internet outages disrupting sales. Additionally, most systems that process credit cards through the Internet (such as CyberCash) charge a per-transaction fee, while HKS charges only for the CCVS software. If the system is not running on the Internet, there's no need for an Internet connection. This can reduce monthly costs and improve security.
HKS first began using Linux in 1995 and now uses it for product development and payment processing for its own customers, as well as testing and demonstration. HKS also makes use of Linux internally for its web server, mail gateway, database server, router, dial-in server and masquerading proxy firewall.
HKS chose Linux as its primary operating system because it liked Linux's versatility, flexibility, open-source code, hardware independence, platform support and low cost. The low cost of Linux allows HKS to run on inexpensive hardware, while compatibility with UNIX systems made Linux an ideal development platform. Access to the Linux kernel source code, especially for serial drivers, made Linux even more attractive. Linux's conformance to the POSIX standard also makes porting to other systems very easy.
HKS is committed to supporting as many versions of Linux as possible. This includes distributions from Red Hat, SuSE, Debian, Caldera, Yellow Dog, NetWinder and Cobalt. In addition to Linux, CCVS runs on a variety of other operating systems including BSDI, AIX, FreeBSD, Digital UNIX, SCO OpenServer and SPARC Solaris.
CCVS can be integrated into almost any application because of the wide variety of languages supported. Developers can choose from C, Tcl, Perl5, Python, Java and PHP3.
HKS customers agree that Linux makes good business sense. Approximately 70 to 80% of HKS customers are Linux users (followed by Solaris and FreeBSD users). In fact, many customers choose CCVS because it is the only payment-processing system designed to operate under Linux.
As the first company to develop a commercial credit-card processing system for Linux, HKS is committed to the Open Source movement and plans to sponsor various open-source projects.
HKS provides a downloadable demo of CCVS. Pricing starts at $995 for Linux or OpenBSD and $1295 for commercial UNIX.
|Designing Electronics with Linux||May 22, 2013|
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
- Designing Electronics with Linux
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Dynamic DNS—an Object Lesson in Problem Solving
- Validate an E-Mail Address with PHP, the Right Way
- What's the tweeting protocol?
- Mediated Reality: University of Toronto RWM Project
- New Products
- Using Salt Stack and Vagrant for Drupal Development
- Dart: a New Web Programming Experience
- OpenOffice.org Off-the-Wall: ToCs, Indexes and Bibliographies in OOo Writer
56 min 56 sec ago
- Kernel Problem
10 hours 59 min ago
- BASH script to log IPs on public web server
15 hours 26 min ago
19 hours 2 min ago
- Reply to comment | Linux Journal
19 hours 34 min ago
- All the articles you talked
21 hours 58 min ago
- All the articles you talked
22 hours 1 min ago
- All the articles you talked
22 hours 2 min ago
1 day 2 hours ago
- Keeping track of IP address
1 day 4 hours ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?