Difference between revisions of "Payment Gateways"
From WHMCS Documentation
(→Third Party Gateways) |
|||
| Line 7: | Line 7: | ||
*'''Convert To For Processing''' – This option is for when using multiple currencies. It is possible that not every gateway you use will accept all the currencies you offer on your site and so for those that don’t, you can choose a currency here for WHMCS to convert to before sending to them. For example if using Google Checkout with a UK account but offering prices in GBP & USD, you would need to select GBP in the Convert To box. This will use the rates set in Config > Currencies to do the conversion which can be set to auto update daily. | *'''Convert To For Processing''' – This option is for when using multiple currencies. It is possible that not every gateway you use will accept all the currencies you offer on your site and so for those that don’t, you can choose a currency here for WHMCS to convert to before sending to them. For example if using Google Checkout with a UK account but offering prices in GBP & USD, you would need to select GBP in the Convert To box. This will use the rates set in Config > Currencies to do the conversion which can be set to auto update daily. | ||
| − | The following is a list of the payment gateways that are supported. Merchant Gateways store credit card information securely in the WHMCS database whilst Third Party Gateways take the client to the provider's website to enter their payment details. | + | The following is a list of the payment gateways that are supported. Merchant Gateways store credit card information securely in the WHMCS database whilst Third Party Gateways take the client to the provider's website to enter their payment details. Tokenisation are a happy medium where repeat billing is possible by storing the original transaction details or a reference number, not the full credit card number, thus reducing your PCI liabilities. |
==Merchant Gateways== | ==Merchant Gateways== | ||
| Line 27: | Line 27: | ||
* Merchant Partners | * Merchant Partners | ||
* [[Offline Credit Card]] | * [[Offline Credit Card]] | ||
| + | |||
| + | ==Tokenisation Gateways== | ||
| + | * [[Authorize.net CIM]] | ||
| + | * Quantum Vault | ||
| + | * SagePay Repeats | ||
| + | * Bluepay Remote | ||
| + | |||
==Third Party Gateways== | ==Third Party Gateways== | ||
| Line 76: | Line 83: | ||
* NETbilling | * NETbilling | ||
* Authorize.net Echeck | * Authorize.net Echeck | ||
| − | |||
* Liberty Reserve | * Liberty Reserve | ||
Revision as of 22:19, 2 March 2011
We have prepared a video tutorial for this section @ http://www.whmcs.com/tutorials.php?i=3
Payment gateways can be setup in Setup > Payment Gateways. Each gateway has it’s own specific data requirements in order to process transactions so they will vary from gateway to gateway. However, all gateways have 3 core fields:
- Show on Order Form – Checking this box will mean it can be shown on the order form as an option – subject to product group gateway restrictions
- Visible Name – The name that is used for this gateway throughout the system and to clients (eg. gateway can be Authorize.net, visible name might be Credit Card)
- Convert To For Processing – This option is for when using multiple currencies. It is possible that not every gateway you use will accept all the currencies you offer on your site and so for those that don’t, you can choose a currency here for WHMCS to convert to before sending to them. For example if using Google Checkout with a UK account but offering prices in GBP & USD, you would need to select GBP in the Convert To box. This will use the rates set in Config > Currencies to do the conversion which can be set to auto update daily.
The following is a list of the payment gateways that are supported. Merchant Gateways store credit card information securely in the WHMCS database whilst Third Party Gateways take the client to the provider's website to enter their payment details. Tokenisation are a happy medium where repeat billing is possible by storing the original transaction details or a reference number, not the full credit card number, thus reducing your PCI liabilities.
Contents
Merchant Gateways
- Authorize.net
- Quantum Gateway
- BluePay
- Payflow Pro
- PayPal Payments Pro
- eWay
- eProcessingNetwork
- InternetSecure
- LinkPoint (First Data Global Gateway)
- SecPay
- ProtX
- PSIGate
- WorldPay Invisible
- NaviGate
- Netregistry Pay
- Merchant Partners
- Offline Credit Card
Tokenisation Gateways
- Authorize.net CIM
- Quantum Vault
- SagePay Repeats
- Bluepay Remote
Third Party Gateways
- PayPal
- ChronoPay
- 2CheckOut
- Google CheckOut
- WorldPay
- E-Gold
- Gate2Shop
- F2B
- PagSeguro
- NoChex
- AlertPay
- ProtX VPS Form
- Paymex
- CashU
- Liberty Reserve
- StormPay
- Paymate AU & NZ
- Payson
- BRPay
- Boleto
- MoneyBookers
- PayOffline (UK Only)
- Mail In Payment
- Bank Transfer
- USA ePay
- e-Path
- iDeal
- WorldPay FuturePay
- Turkish Finansbank
- Pay Junction
- BidPay
- CCAvenue
- OpenECHO
- Turkish Garanti Bank
- NTPNow
- SecurePay
- WorldPay Invisible XML
- ACHDirect
- FastHosts
- Camtech
- SecurePay AU
- Optimal Payments
- Paymate
- AsiaPay
- PayPal Website Payments Pro
- NETbilling
- Authorize.net Echeck
- Liberty Reserve
Test Credit Card Numbers
Gateways often have test modes where you can use test card numbers. The common test card numbers are below and should generate successful test transactions but they can vary from gateway to gateway. You may use any expiration date in the future.
4007000000027 - Visa Test Card 4012888818888 - Visa Test Card II 5424000000000015 - MasterCard Test Card 370000000000002 - American Express Test Card 6011000000000012 - Discover Test Card 3088000000000017 - JCB Test Card (Use expiration date 0905) 38000000000006 - Diners Club/Carte Blanche Test (Use expiration date 0905)