We often get asked, "What is a Payment Gateway?" or "How is a payment gateway different from a merchant account or a credit card processor?"
Most clients asking these questions are ecommerce merchants in need of some type of online payment integration. This means that they have a certain software or shopping cart in mind and are trying to find a way to integrate credit card processing into it.
Below is an explanation of payment gateways and how they fit into the ecosystem of credit card processing.
Payment Gateway vs. Virtual Terminal
The difference is simple: One is used by computer programs, the other is used by humans. Both have the same purpose: to accept an incoming credit card transaction and process it.
A Virtual Terminal is a user-interface (often web-based) that allows merchants to log in and manually process a credit card payment. It is great for humans, but not made for programs to interact with.
A payment gateway (sometimes referred to as a payment API or RESTful API) is a specific URL that has no user-interface but is designed to receive an incoming transaction message.
Merchant Account + Payment Gateway = Most Credit Card Processors
Most credit card processors, including Helcim, offer their ecommerce clients both the merchant account and the payment gateway service together. The few processors that don't have their own payment gateway will often resell a third-party payment gateway service as part of their buddle. That's because an ecommerce merchant account without a payment gateway is useless, as the merchant account has no means of receiving transactions.
What is a Payment Gateway-Only Service?
Some companies such as Authorize.NET and CyberSource are referred to as "payment gateway-Only" service providers. This means that they offer their payment gateway service without the merchant account portion. So why would you pay for a payment gateway-only service? There are some instances that require it:
The software or shopping cart you are using is not compatible with your processor's payment gateway but is compatible with a payment gateway-only service. This is a common usage of Authorize.NET, being the most commonly integrated payment gateway.
No Processor Payment Gateway
The provider does not have their own payment gateway. These merchant account providers will rely on reselling third-party payment gateways instead of developing their own payment gateway.
The built-in payment gateway offered by your credit card processor does not have all the features you need. Some payment gateway-only service providers offer features such as card-tokenization and advanced fraud-protection that are beyond what most regular payment gateways offer.
The main downside of using a payment gateway-only service is that the merchant incurs fees from both the credit card processor and the payment gateway company. However, for some merchants, the benefits of the seamless payment integration warrant the additional costs.
Why isn't Payment Integration Simpler?
Everyone wants to do things their own way. There are dozens of acquiring banks, hundreds of credit card processors and thousands of various software and shopping carts, each with their own unique API formats.
The message structures are different (e.g. XML vs POST array), the required fields are different and even the variable names vary greatly. With no standardized formats, it is the payment gateway's mission to navigate these waters and properly translate the data.
Is my Software or Shopping Cart Compatible with my Credit Card Processor?
The easiest way to find out is to search for the software name followed by the words payment gateway, such as "Mal's E-commerce payment gateways". Most software providers will have a web page dedicated to listing all the payment gateways they've integrated. If your desired credit card processor isn't listed, look for generic payment gateways such as Authorize.NET and find out if your processor supports these.