Information on Merchant Accounts,
Ecommerce and Credit Card Processing


August 30th, 2006 by Jamie Estep

Payment Gateways and SSL Certificates (API vs. Simple)

Filed in: Ecommerce | 3 comments

I have been very busy lately, which has resulted in a reduced quantity / quality of posts. The site just got switched to a new server and everything should run much more smoothly now.

I often run into website owners that are confused about the SSL requirements a website must have to process payments. Specifically, why would a SSL certificate be required if a website is using a payment gateway.

The answer to this is simple. Payment gateways are independent of SSL certificates and do nothing themselves to make a website secure. However, some Payment Gateways do not use an API (Application Program Interface) method to integrate with a website. A SSL certificate is normally not required if a website is not using an API method and not processing a customer’s credit card on their own site. Instead, the website’s visitor is redirected to a secure checkout page on the domain of the payment gateway. I think this redirection is where the main confusion is created.

Types of payment gateway integration:
Basic Integration – A website visitor browses and adds products to a shopping cart on a website. When they go to pay for their selected merchandise, they are redirected to a secure web page that is hosted with the payment gateway.

API Integration – This is a more advanced and better integration. The website is connected securely to the payment gateway. The visitors shops on the website, and makes payment on the same website. This is a completely seamless integration, and the website must have the ability to provide a secure connection between the user, in addition to a secure connection between the website and the payment gateway.

API vs Simple Integration Methods

Which method is better:
There are benefits to both integration methods, but I think that the API integration method is much better that the simple method. API integration keeps a visitor on the same website that they are shopping with, it allows for easier visitor and order tracking, and is generally a much better practice for usability concerns. If you look at any major ecommerce website out there, you will find that they use the API version of whichever payment gateway they are using.

The simple method is easier to implement, and doesn’t require a SSL certificate. The drawbacks are mainly the loss of control of website visitors when they go to make a purchase, difficulty in tracking user behavior on a website since they leave it before a conversion is completed, lack of control over the payment abilities of a website, and poor website usability.

Many websites start out using a simple method of integration, but will later want the added capabilities of the API version.

I recommend using the payment gateway using the AIM API integration method for any business.

3 Responses to “Payment Gateways and SSL Certificates (API vs. Simple)”

  1. Payment Processing Gateway May 27, 2009 at 12:41 am

    Thank you for sharing this information… I’ve come across many people who wonder which method is better..

  2. Merchant Payment Gateway July 27, 2009 at 5:24 am

    Now-a-days, payment gateways are independent of SSL certificates and do nothing themselves to make a website secure. However, some Payment Gateways do not use an API method to integrate with a website.

  3. SureGate May 17, 2010 at 4:30 pm

    This is true, API is a much simpler way to intergrate a shopping cart to a Payment Gateway. My company currently has our own API.


Merchant Equipment Store
5725 W Highway 290, Ste 105
Austin, Texas 78735

Customer Service Ask a Question
About Us
Contact Us
Privacy and Store Policies

Tools and Calculators Credit Card Logos
Simple Fee Calculator
Advanced Fee Calculator
Lease Cost Calculator
Voided Check Creator

Need Some Help? Information Center
Merchant Account FAQ's
Compare Popular Terminals
Credit Card Machines
Recommended Services

Copyright © 2015 The Merchant Account Blog, all rights reserved. Theme design by Jamie Estep.