Difference between revisions of "WorldPay"
Line 7: | Line 7: | ||
==Setting up the gateway== | ==Setting up the gateway== | ||
− | You first need to activate the WorldPay and/or WorldPay FuturePay module(s) in WHMCS by navigating to '''Setup > Payment Gateways''' and enter your details as requested. | + | You first need to activate the WorldPay and/or WorldPay FuturePay module(s) in WHMCS by navigating to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Payment Gateways''' or, prior to WHMCS 8.0, '''Setup > Payment Gateways''' and enter your details as requested. |
− | Next | + | Next log in to the WorldPay Merchant Administration Interface > System Settings > Integration Setup : PRODUCTION and set the Payment Response URL to: |
<WPDISPLAY ITEM=MC_callback> | <WPDISPLAY ITEM=MC_callback> | ||
You should also tick the following items: Payment Response enabled?, Enable Recurring Payment Response and Enable the Shopper Response. | You should also tick the following items: Payment Response enabled?, Enable Recurring Payment Response and Enable the Shopper Response. | ||
Line 24: | Line 24: | ||
If using FuturePay, in the Auth Password field, you'll need to enter the password that is setup to allow remote charges to be made. This is also referred to as the Invisible Auth Password and requires that a Remote Admin installation is added to your WorldPay account. This can be achieved by emailing support [at] worldpay [dot] com with your company ID and requesting this (at no extra cost). | If using FuturePay, in the Auth Password field, you'll need to enter the password that is setup to allow remote charges to be made. This is also referred to as the Invisible Auth Password and requires that a Remote Admin installation is added to your WorldPay account. This can be achieved by emailing support [at] worldpay [dot] com with your company ID and requesting this (at no extra cost). | ||
− | You should then go to '''Setup > Payment Gateways''' and setup the FuturePay gateway as show below: | + | You should then go to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Payment Gateways''' or, prior to WHMCS 8.0, '''Setup > Payment Gateways''' and setup the FuturePay gateway as show below: |
[[Image:Futurepay_setup.gif]] | [[Image:Futurepay_setup.gif]] |
Revision as of 13:26, 5 August 2020
Contents
Supported Features
Type | One Time | Recurring | Refunds | Reversals |
---|---|---|---|---|
3rd Party | Yes | No | No |
No |
There are two modules for worldpay - one time invoices and FuturePay. For FuturePay, we use the more versatile Limited Agreements payment system. This offers the ultimate in flexibility and allows charges to be taken from the clients card whenever they are needed. So with this, once the user has setup a FuturePay Agreement, any invoice can be charged to their card at any time. This makes all invoice payments automated. There are however some steps involved in configuring it and we'll go through these below.
Setting up the gateway
You first need to activate the WorldPay and/or WorldPay FuturePay module(s) in WHMCS by navigating to Configuration () > System Settings > Payment Gateways or, prior to WHMCS 8.0, Setup > Payment Gateways and enter your details as requested.
Next log in to the WorldPay Merchant Administration Interface > System Settings > Integration Setup : PRODUCTION and set the Payment Response URL to:
<WPDISPLAY ITEM=MC_callback>
You should also tick the following items: Payment Response enabled?, Enable Recurring Payment Response and Enable the Shopper Response.
FuturePay Specific Items
Supported Features
Type | One Time | Recurring | Refunds | 3D Secure |
---|---|---|---|---|
Token | Yes | Yes | No | No |
Remote Update Card | Remote Delete Card | AddPayMethod API |
---|---|---|
No | No | No |
If using FuturePay, in the Auth Password field, you'll need to enter the password that is setup to allow remote charges to be made. This is also referred to as the Invisible Auth Password and requires that a Remote Admin installation is added to your WorldPay account. This can be achieved by emailing support [at] worldpay [dot] com with your company ID and requesting this (at no extra cost).
You should then go to Configuration () > System Settings > Payment Gateways or, prior to WHMCS 8.0, Setup > Payment Gateways and setup the FuturePay gateway as show below:
Once a client makes the first payment (usually at the time of ordering) the FuturePay ID is stored in the database (tblclients.gatewayid).
The Futurepay ID is displayed to staff on the invoice page and also by clicking the Credit Card Information link on the client's Summary tab.
Auth Mode A - Capture Delay
The auth mode is used to turn on capture delay. A = on. You then configure the delay period in the WorldPay admin. This used to be called pre-auth mode. Capture Delay enables you to specify a delay between the authorisation of a payment and its capture. This can be helpful when determining whether you should fulfil an order since it allows you time to assess a transaction. You can cancel (void) a transaction through the WorldPay Merchant Interface before capture, thereby saving you time and money by avoiding making a refund.
When enabled, the client will not be able to tell whether you are using capture delay as it behaves exactly the same; invoices in WHMCS will still instantly be marked as paid and all automation will take place as normal.
For example; a customer makes a payment and you want to Worldpay to automatically debit this payment from the customers' card then you would turn off capture delay. If you want to delay the capture then turn it on.
To automatically capture all payments without any delay
Set Capture Delay in your WorldPay account to 0 (zero) - set AuthMode on your Payment Gateway page to A.
To automatically capture all payments with a delay of 1-14 days
Set Capture Delay in your WorldPay account to a number 1-14 - set AuthMode on your Payment Gateway page to A.
To turn off automatic payment capture and manually capture all payments
Set Capture Delay in your WorldPay account to OFF - set AuthMode on your Payment Gateway page to E.
Server Modules
cPanel/WHM - DirectAdmin - Plesk - Helm 3 - Helm 4 - Ensim - InterWorx - WebsitePanel - Cloudmin
Lxadmin - Virtualmin Pro - XPanel - HyperVM - SolusVM - Cloudmin - WHMSonic - VPS.Net
CentovaCast - SCPanel - MediaCP - GameCP - TCAdmin - Reseller Central - Auto Release - Heart Internet
Registrar Modules
Enom - ResellerClub - Nominet - OpenSRS - ResellOne - OnlineNIC - PlanetDomain - Affordable Domains
TPP Wholesale - TPPInternet - Stargate - Namecheap - NetEarthOne - Bizcn - InternetBS - GMO Internet
12Register - Registercom - DotDNS - WebNIC - Dot.TK - HexoNet - Realtime Register - Registereu
RRPProxy - ResellerCamp - TransIP - Heart Internet - IPMirror - NetRegistry - OVH - VentraIP Wholesale
Email - 101Domain
Fraud Modules
MaxMind - VariLogiX FraudCall - Telesign
Gateway Modules
2CheckOut - AsiaPay - Auth.net Echeck - Authorize.net - Authorize.net CIM - Bank Transfer - BidPay
BluePay - BluePay Echeck - BluePay Remote - Boleto - CashU - CC Avenue - ChronoPay - Direct Debit
EMatters - E-Path - eProcessingNetwork - eWAY Tokens - F2B - Finansbank - GarantiBank - Gate2Shop
Inpay - InternetSecure - IP.Pay - Kuveytturk - Modulo Moip - Mail In Payment - Merchant Partners
Merchant Warrior - IDEALMollie - Moneris - Moneris Vault - Skrill 1-Tap - NaviGate - NETbilling
Netregistry Pay - NoChex - Offline Credit Card - Optimal Payments - PagSeguro - Payflow Pro - Pay Junction
Paymate AU and NZ - Payment Express - PayPal - PayPal Card Payments - PayPal Express Checkout
PayPal Payments - PayPal Payments Pro - PayPoint.net (SecPay) - Payson - Planet Authorize - ProtX VSP Form
PSIGate - Quantum Gateway - Quantum Vault - SagePay - SagePay Tokens v2 - SecurePay
SecurePay AU - Secure Trading - TrustCommerce - USA ePay - WorldPay - WorldPay Invisible