Payment Gateways

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 4 core options:

• 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.

Deactivate Gateway

• Deactivate - Should you no longer wish to use a particular payment gateway clicking the red (Deactivate) link beside its name will gracefully remove the gateway from use thus preventing further payments being made using this method. A popup message will appear prompting selection of a new gateway to which services, domains and unpaid invoices will be assigned, as a result no further payments will be made using the deactivated gateway and any services previously assigned to it will use the new gateway in future.

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 Gateways 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

• Authorize.net
• BluePay
• eProcessingNetwork
• eWay
• InternetSecure
• LinkPoint (First Data Global Gateway)
• Merchant Partners
• Moneris
• NaviGate
• Netregistry Pay
• Offline Credit Card
• Payflow Pro
• PSIGate
• PayPal Payments Pro
• Quantum Gateway
• SecPay
• SagePay
• WorldPay Invisible

Tokenisation Gateways

• Authorize.net CIM
• Bluepay Remote
• Merchant Warrior Token Payments
• Moneris Vault
• PayPal Pro Reference Payments
• Quantum Vault
• SagePay Repeats
• WorldPay FuturePay

Third Party Gateways

PayPal	2CheckOut	Google CheckOut
NoChex	WorldPay	Mail In Payment
Bank Transfer	ACHDirect	AlertPay
Amazon Simple Pay	AsiaPay	Authorize.net Echeck
BidPay	BluePay Echeck	BluePay Remote
Boleto	CC Avenue	Camtech
CashU	ChronoPay	Cobrança - F2b
CyberBit	E-Gold	e-Path
eMatters	FastHosts	Gate2Shop
iDEAL	iDEAL via Mollie	inpay
IP.Pay	Kuveytturk Bank	Liberty Reserve
Merchant Partners	Merchant Warrior	Moneris
Moneybookers	NETbilling	NTPNow
NaviGate	Netregistry Pay	OpenECHO
Optimal Payments	PagSeguro	Pay Junction
Pay Offline	PayPal Express Checkout	Paymate
Paymate NZ	Payment Express	Paymex
Payson	PlanetAuthorize	ProtX VSP Form
SecurePay	SecurePay AU	StormPay
TrustCommerce	Turkish Finansbank	Turkush Garanti Bank
USA ePay	WorldNet	WorldPay

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)