Sites that sell goods or services need a way to collect payments. In many cases, such vendors can utilize existing services offered by their shopping host, for example Amazon.com sellers can use the Amazon payment system. Other vendors with custom websites need to find payment alternatives.

I've used Authorize.net for two clients so far, and in those cases it works well. Authorize.net handles the transactions and forwards settled payments to the client's bank account. Briefly, a website can provide goods or services, and when it is time to collect payment, they provide a payment link on their site that seamlessly sends the user to the authorize.net payment form. This form is generic but relatively customizable, including support for the client logo/banner. Upon completion of the transaction, the user can return to the client's site via a link on the receipt page.

Behind the scenes, the authorize.net-server sends the client-server payment confirmation, and PHP scripts are used to update the client's database and otherwise finish processing the order.

One nice benefit for small businesses is that they do not have to store or manage sensitive customer data, therefore avoiding stringent annual system audits by the banking industry. All credit card and billing information is input and processed on the secure authorize.net server, which offers the option to store that data for future transactions or not store it. Other features include a recurring billing option and additional security safeguards.

If your website needs a payment gateway, please consider SBCast.com for PHP-MySQL development.