Last updated June 10, 2013. Created by peterx on November 20, 2011.
Edited by rcross. Log in to edit this page.

You want to sell something and collect payment using a credit card facility or equivalent. You need a payment gateway.

This page is to explain some terminology and summarise the available modules. Child pages can go into more detail about the technical aspects of specific modules.

2nd or 3rd party?

Payment gateways are either second or third party gateways. The first party is the person making the payment. Your site is the second party. The bank providing the merchant facility is the third party.

In a third party system, you build the shopping cart on your Web site then calculate the total including all shipping charges, fees, and taxes. You then pass the transaction to the bank Web site. The bank accepts the credit card payment then returns an authorisation number to your site. You then continue the checkout process.

In a second party system, your Web site accepts the credit card details and passes them to the bank without your customer seeing the bank Web site. Second party systems are hard to set up because the bank will impose strict security requirements and audit your site. You are also responsible for handling credits and a whole lot of things not needed for third party systems.

3rd party gateway modules

Commerce eWay works in D7 and has 74 users. eWay is an independent gateway covering many banks and financial institutions in Australia

Ubercart eWay Payment Gateway works in D6 and D7 and has 160 users. eWay is an independent gateway covering many banks and financial institutions in Australia

Ubercart MIGS Gateway works on D5, D6, and D7. Has 46 sites using it. MIGS is the Mastercard gateway used by some banks in Australia.

2rd party gateway modules

Ubercart Dialect MIGS Payment Gateway works on D6 and has 19 sites using it. MIGS is the Mastercard gateway used by some banks in Australia.

Looking for support? Visit the Drupal.org forums, or join #drupal-support in IRC.