Difference between revisions of "GoCardless"

From WHMCS Documentation

(Charge Date Preference)
Line 1: Line 1:
 +
== About this Module ==
 +
 +
<div class="docs-alert-success">
 +
We added this payment gateway in WHMCS 7.7.
 +
</div>
 +
 +
[https://gocardless.com GoCardless] is a payment gateway which allows for direct debit payments to be automated electronically.
 
{{gateways
 
{{gateways
 
| onetime = yes
 
| onetime = yes
Line 4: Line 11:
 
| reversals = yes
 
| reversals = yes
 
}}
 
}}
 +
== Adding the GoCardless Payment Gateway ==
  
<div class="docs-alert-info"><i class="fa fa-info-circle"></i> This page describes a payment gateway available in WHMCS version 7.7 and above.</div>
+
To set up the GoCardless payment gateway in WHMCS:
 +
 +
# Make certain that your WHMCS installation uses an HTTPS-secured connection. If you do not, this payment gateway will not function. You can purchase an SSL certificate [https://www.whmcs.com/ssl-certificates here].
 +
# Go to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > [[Payment Gateways]]''' or, prior to WHMCS 8.0, '''Setup > Products/Services > Payment Gateways'''.
 +
# Choose the '''All Payment Gateways''' tab.
 +
# Click '''GoCardless'''. The WHMCS GoCardless app will appear.
 +
# Either sign up for a new account or sign in to your existing account. The system will automatically configure GoCardless for you. [[File:Gocardless-config.png]]
 +
# Optionally, enter a custom name for the gateway for each of your supported currencies.
 +
# Check '''Show on Order Form''' to display this payment method in the Client Area during checkout.
 +
# In WHMCS 8.0 and later, check '''Charge Date Preference''' if you want to initiate payment capture immediately after invoice generation. By default, if you do not check this, the GoCardless charge date will be the due date for the invoice.
 +
# Click '''Save Changes'''.
  
[https://gocardless.com GoCardless] is a payment gateway which allows for direct debit payments to be automated electronically.
+
=== Supported Currencies ===
 +
 
 +
GoCardless only support the following currencies:  
 +
 
 +
* 'AUD'
 +
* 'CAD'
 +
* 'DKK'
 +
* 'EUR'
 +
* 'GBP'
 +
* 'NZD'
 +
* 'SEK'
 +
* 'USD' <div class="docs-alert-info">We added support for USD in WHMCS 7.9.</div>
  
==Getting Started==
+
Clients who do not use one of these currencies cannot make payments using GoCardless.
To activate the GoCardless module in WHMCS, navigate to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Payment Gateways''' or, prior to WHMCS 8.0, '''Setup > Payments > Payment Gateways'''. Then, choose GoCardless from the All Payment Gateways tab.
 
  
Upon clicking, you will be redirected to link you account to WHMCS GoCardless App. On the page displayed, it is possible to sign-up for a new account or sign-in to an existing account. Once signed up, you will be redirected back to your WHMCS installation where you can customise the display name of the module.
+
==Payment Workflow==
  
====Automatic Configuration====
+
When the first payment is made, a mandate is set up with the client's bank. This typically takes a few days, so the invoice will change from '''Unpaid''' to '''Payment Pending''' status. At this point, you can view the mandate details and expected payment completion date by viewing the invoice. As soon as the mandate is set up and the first payment has cleared, the invoice's status will change to '''Paid''' and the service will be provisioned by WHMCS automatically.
There is no manual configuration required for the GoCardless Payment Module. All configuration fields will be filled automatically when redirected back to the WHMCS installation.
 
  
[[File:Gocardless-config.png]]
+
When the renewal invoice is generated for a recurring service, a capture attempt will be made against the mandate in accordance with '''Process Days Before Due''' in '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Automation Settings''' or, prior to WHMCS 8.0, '''Setup > Automation Settings'''. As it can take a few days for the payment to complete, we recommend a setting of '''3'''. This way, 3 days before the invoice '''Due Date''', the payment process will be initiated by the cron and the invoice status updated from '''Unpaid''' to '''Payment Pending'''. Payment should then complete on the invoice '''Due Date''' and the invoice will be marked '''Paid''' once the payment has cleared.
  
For each supported currency and scheme enabled a custom name can be defined that will be displayed to clients wherever the available payment gateways are listed. This allows for naming that provides a more friendly and recognisable name based on the customers location, for example "Direct Debit" for UK/GBP customers, "ACH" for US/USD customers, etc...
+
Once a mandate has been created, WHMCS can use it for processing renewal payments for any other services associated with the client as long as they are set to the GoCardless gateway as well.
  
===Supported Currencies===
+
When making a manual payment, customers are able to select to use a previously stored bank account or enter a new one.
GoCardless only support the following currencies: 'AUD', 'CAD', 'DKK',  'EUR',  'GBP', 'NZD', 'SEK', and 'USD'. Any clients not using one of these currencies will be unable to make a payment using GoCardless and will receive an appropriate message.
 
  
<div class="docs-alert-info"><i class="fa fa-info-circle"></i> Support for USD was added in WHMCS 7.9.</div>
+
Customers never leave your WHMCS installation during checkout or adding/removing a new bank account. Personal bank information is submitted directly to GoCardless and is never stored in your local WHMCS installation.
  
===SSL Requirement===
+
==Reversed Payments==
  
GoCardless requires an HTTPS secured connection for the WHMCS installation that customers will be returned to following setup of a mandate. If the domain your WHMCS installation is installed on does not have a valid SSL Certificate, the payment return will not work.
+
The Direct Debit Guarantee scheme allows the payee to file a claim for any payment taken in error. WHMCS will monitor for ''charged_back'' events from GoCardless and will automatically process these as appropriate.
  
If you need to purchase an SSL Certificate, you can do so at [https://www.whmcs.com/ssl-certificates www.whmcs.com/ssl-certificates]
+
To learn more, visit [[Payment Reversals]]
  
==Payment Workflow==
+
==Refunding Payments==
When the first payment is made, a mandate is set up with the client's bank. This typically takes a few days, so the invoice will change from '''Unpaid''' to '''Payment Pending''' status.
 
At this point you can view the mandate details and expected payment completion date by viewing the invoice. As soon as the mandate is set up and the first payment has cleared, the invoice's status will change to '''Paid''' and the service will be provisioned by WHMCS automatically.
 
  
When the renewal invoice is generated for a recurring service, a capture attempt will be made against the mandate in accordance with '''Process Days Before Due''' in '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Automation Settings''' or, prior to WHMCS 8.0, '''Setup > Automation Settings'''. As it can take a few days for the payment to complete, we recommend a setting of '''3'''. This way, 3 days before the invoice '''Due Date''', the payment process will be initiated by the cron and the invoice status updated from '''Unpaid''' to '''Payment Pending'''. Payment should then complete on the invoice '''Due Date''' and the invoice will be marked '''Paid''' once the payment has cleared.
+
While refunds with GoCardless are not directly supported from within WHMCS, they can still be processed directly with GoCardless on a case-by-case basis through their review and approval process.
  
Once a mandate has been created, WHMCS can use it for processing renewal payments for any other services associated with the client as long as they are set to the GoCardless gateway as well.
+
Please refer to the [https://support.gocardless.com/hc/en-ca/articles/210536269-Refunding-payments refunding payments] section of the GoCardless documentation.
  
When making a manual payment, customers are able to select to use a previously stored bank account or enter a new one.
+
== Mandates ==
  
Please note that customers never leave your WHMCS installation during checkout or adding/removing a new bank account. Personal bank information is submitted directly to GoCardless and is never stored in your local WHMCS installation.
+
<div class="docs-alert-success">
 +
We added these features in WHMCS 7.8.
 +
</div>
  
==Charge Date Preference==
+
=== Reinstating Mandates ===
  
<div class="docs-alert-warning"><i class="fa fa-info-circle"></i>  
+
<div class="docs-alert-warning">
This section describes a feature available in WHMCS version 8.0 and above.
+
Reinstating mandates requires specific permission from GoCardless.
 
</div>
 
</div>
  
By default, payment capture attempts will set the GoCardless Charge Date to the due date for an invoice. Enabling this setting on the GoCardless module will instead initiate the payment capture immediately on invoice generation.
+
When a mandate has been accidentally cancelled, WHMCS can initiate steps to reinstate the mandate without having the client set it up again.
  
 
To do this:
 
To do this:
  
# Navigate to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Payment Gateways''' or, prior to WHMCS 8.0, '''Setup > Payments > Payment Gateways'''.  
+
# Go to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Payment Gateways''' or, prior to WHMCS 8.0, '''Setup > Payments > Payment Gateways'''.  
 
# Click the '''Manage Existing Gateways''' tab.  
 
# Click the '''Manage Existing Gateways''' tab.  
# Check '''Charge Date Preference'''.
+
# Click '''Manage Cancelled Mandates'''.
# Save your changes.
+
# Follow the instructions in the modal that appears to reinstate a cancelled mandate.
  
==Reversed Payments==
+
=== Importing Existing Mandates ===
  
The Direct Debit Guarantee scheme allows the payee to file a claim for any payment taken in error. WHMCS will monitor for ''charged_back'' events from GoCardless and will automatically process these as appropriate.
+
<div class="docs-alert-info">
 +
You must disable any automatically-charged mandates that you import in order to prevent possible duplicate charges.
 +
</div>
  
To learn more, visit [[Payment Reversals]]
+
You can import mandates that you set up outside of WHMCS and associate them with a client.
  
==Refunding Payments==
+
To do this:
  
While refunds with GoCardless are not directly supported from within WHMCS, they can still be processed directly with GoCardless on a case-by-case basis through their review and approval process.
+
# Go to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Payment Gateways''' or, prior to WHMCS 8.0, '''Setup >  Payments > Payment Gateways'''.
 +
# Click the '''Manage Existing Gateways''' tab.
 +
# Click '''Import Existing Mandates'''.
 +
# Follow the instructions in the modal that appears to import a active mandate to a specific client.
  
Please refer to the [https://support.gocardless.com/hc/en-ca/articles/210536269-Refunding-payments refunding payments] section of the GoCardless documentation.
+
== Reconfiguring Callbacks ==
  
==Reinstate Mandate==
+
After moving WHMCS, you must perform the following steps:
<div class="docs-alert-warning"><i class="fa fa-info-circle"></i> This section describes a feature available in WHMCS version 7.8 and above.</div>
 
<div class="docs-alert-info">
 
<span class="title">Permission Required:</span><br />
 
Reinstating Mandates requires specific permission from GoCardless
 
</div>
 
When a mandate has been accidentally cancelled, WHMCS can initiate steps to reinstate the mandate without having the client set it up again.
 
Navigate to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Payment Gateways''' or, prior to WHMCS 8.0, '''Setup >  Payments > Payment Gateways'''. Click the '''Manage Existing Gateways''' tab. Click on the '''Manage Cancelled Mandates''' button and follow the instructions in the modal that appears to reinstate a cancelled mandate.
 
  
==Import Existing Mandates==
+
# Go to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Payment Gateways''' or, prior to WHMCS 8.0, '''Setup >  Payments > Payment Gateways'''.
<div class="docs-alert-warning"><i class="fa fa-info-circle"></i> This section describes a feature available in WHMCS version 7.8 and above.</div>
+
# Click '''Configure GoCardless Account Connection'''.
<div class="docs-alert-info"><i class="fa fa-info-circle"></i> If any of the mandates being imported are set to be automatically charged by GoCardless, that will need to be disabled to prevent possible duplicate charges.</div>
+
# Log in again using the same details.  
For mandates that have been setup outside of WHMCS, they can be imported and associated with a client.
 
Navigate to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Payment Gateways''' or, prior to WHMCS 8.0, '''Setup >  Payments > Payment Gateways'''. Click the '''Manage Existing Gateways''' tab.
 
Click on the '''Import Existing Mandates''' button and follow the instructions in the modal that appears to import a active mandate to a specific client.
 
  
==Reconfiguring Callbacks==
+
This ensures that GoCardless stores and uses the new system URL and gateway callback file URL.
After moving WHMCS, it is important that you navigate to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Payment Gateways''' or, prior to WHMCS 8.0, '''Setup >  Payments > Payment Gateways''' and click '''Configure GoCardless Account Connection''' and sign back in using the same details. This will ensure that the new System URL and Gateway callback file URL are stored and used for existing and new mandates going forward.
 
  
 
{{modules}}
 
{{modules}}

Revision as of 19:08, 31 March 2022

About this Module

We added this payment gateway in WHMCS 7.7.

GoCardless is a payment gateway which allows for direct debit payments to be automated electronically.

Supported Features

Type One Time Recurring Refunds Reversals
3rd Party Yes Yes No

Yes

Adding the GoCardless Payment Gateway

To set up the GoCardless payment gateway in WHMCS:

  1. Make certain that your WHMCS installation uses an HTTPS-secured connection. If you do not, this payment gateway will not function. You can purchase an SSL certificate here.
  2. Go to Configuration () > System Settings > Payment Gateways or, prior to WHMCS 8.0, Setup > Products/Services > Payment Gateways.
  3. Choose the All Payment Gateways tab.
  4. Click GoCardless. The WHMCS GoCardless app will appear.
  5. Either sign up for a new account or sign in to your existing account. The system will automatically configure GoCardless for you. Gocardless-config.png
  6. Optionally, enter a custom name for the gateway for each of your supported currencies.
  7. Check Show on Order Form to display this payment method in the Client Area during checkout.
  8. In WHMCS 8.0 and later, check Charge Date Preference if you want to initiate payment capture immediately after invoice generation. By default, if you do not check this, the GoCardless charge date will be the due date for the invoice.
  9. Click Save Changes.

Supported Currencies

GoCardless only support the following currencies:

  • 'AUD'
  • 'CAD'
  • 'DKK'
  • 'EUR'
  • 'GBP'
  • 'NZD'
  • 'SEK'
  • 'USD'
    We added support for USD in WHMCS 7.9.

Clients who do not use one of these currencies cannot make payments using GoCardless.

Payment Workflow

When the first payment is made, a mandate is set up with the client's bank. This typically takes a few days, so the invoice will change from Unpaid to Payment Pending status. At this point, you can view the mandate details and expected payment completion date by viewing the invoice. As soon as the mandate is set up and the first payment has cleared, the invoice's status will change to Paid and the service will be provisioned by WHMCS automatically.

When the renewal invoice is generated for a recurring service, a capture attempt will be made against the mandate in accordance with Process Days Before Due in Configuration () > System Settings > Automation Settings or, prior to WHMCS 8.0, Setup > Automation Settings. As it can take a few days for the payment to complete, we recommend a setting of 3. This way, 3 days before the invoice Due Date, the payment process will be initiated by the cron and the invoice status updated from Unpaid to Payment Pending. Payment should then complete on the invoice Due Date and the invoice will be marked Paid once the payment has cleared.

Once a mandate has been created, WHMCS can use it for processing renewal payments for any other services associated with the client as long as they are set to the GoCardless gateway as well.

When making a manual payment, customers are able to select to use a previously stored bank account or enter a new one.

Customers never leave your WHMCS installation during checkout or adding/removing a new bank account. Personal bank information is submitted directly to GoCardless and is never stored in your local WHMCS installation.

Reversed Payments

The Direct Debit Guarantee scheme allows the payee to file a claim for any payment taken in error. WHMCS will monitor for charged_back events from GoCardless and will automatically process these as appropriate.

To learn more, visit Payment Reversals

Refunding Payments

While refunds with GoCardless are not directly supported from within WHMCS, they can still be processed directly with GoCardless on a case-by-case basis through their review and approval process.

Please refer to the refunding payments section of the GoCardless documentation.

Mandates

We added these features in WHMCS 7.8.

Reinstating Mandates

Reinstating mandates requires specific permission from GoCardless.

When a mandate has been accidentally cancelled, WHMCS can initiate steps to reinstate the mandate without having the client set it up again.

To do this:

  1. Go to Configuration () > System Settings > Payment Gateways or, prior to WHMCS 8.0, Setup > Payments > Payment Gateways.
  2. Click the Manage Existing Gateways tab.
  3. Click Manage Cancelled Mandates.
  4. Follow the instructions in the modal that appears to reinstate a cancelled mandate.

Importing Existing Mandates

You must disable any automatically-charged mandates that you import in order to prevent possible duplicate charges.

You can import mandates that you set up outside of WHMCS and associate them with a client.

To do this:

  1. Go to Configuration () > System Settings > Payment Gateways or, prior to WHMCS 8.0, Setup > Payments > Payment Gateways.
  2. Click the Manage Existing Gateways tab.
  3. Click Import Existing Mandates.
  4. Follow the instructions in the modal that appears to import a active mandate to a specific client.

Reconfiguring Callbacks

After moving WHMCS, you must perform the following steps:

  1. Go to Configuration () > System Settings > Payment Gateways or, prior to WHMCS 8.0, Setup > Payments > Payment Gateways.
  2. Click Configure GoCardless Account Connection.
  3. Log in again using the same details.

This ensures that GoCardless stores and uses the new system URL and gateway callback file URL.

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