For xSPS/Developers

ASP's, ISP's, Web Developers, Web Application Designers and Internet programmers will definitely appreciate the time savings using the oPAYc drivers to integrate real time credit card processing into a web site. Some payment processors are fairly straightforward but most are not despite their claims. The oPAYc driver API is as simple to use as an SQL statement to a database. In most cases it is a single line of code to add to a site to be able to do real time credit card transactions.

To participate, and survive, in today's e-commerce revolution, merchants selling their wares on-line must be able to accept credit cards in an automated manner. Currently it is estimated several hundred "gateway" systems exist which make this possible. Each system has a different interface to allow the merchant's e-commerce application to communicate with it and process financial transactions.

Each system also widely varies in a non-technical manner as well, which includes such parameters as how the fees are calculated. This ranges from large deposits, percentage of sales, flat fee, fee per transaction, monthly fee, to setup fee, etc. Just about every permutation of this is out there. Different systems are more suited to some geographic areas, in terms of the cards they accept and currency they operate in as well.

This presents several problems for e-commerce merchants and system integrators. Since every system has a different widely varying interface, system integrators are often familiar only with a few of the systems, and based on the number available, probably not the one best matched to the client. Some of the systems out there also require a web based client interface to operate. Some require user intervention to process a transaction, so do not support recurring billing. The feature matrix for all of these systems is massive and complex to put it mildly!

Inline's philosophy here is to sort this all out into one standard way of dealing with ALL the various types of systems, and present that to the system integrator in a way which is easy to deal with. The idea is, the integrator implements one standard simple interface in the e-commerce application, and then the oPAYc drivers hide all the low level interaction from there on. The oPAYc drivers are setup in such a way that they may be substituted on a one for one basis to change payment gateways at any time, or to support multiple gateways with different merchant accounts for different purposes simultaneously. The integrator may even choose to provide the application with a select list of all or a subset of all the available drivers to allow the merchant to easily configure the driver of their choice later on if it is not predetermined.
Copyright © 1998-2008 Inline Internet Systems, Inc.