Available on: UK: Go Paperless and above | US and Canada: All-in-one and above
The GoCardless integration lets your customers pay you directly from their bank account. It powers two payment types in Commusoft: automatic recurring payments for contracts, and one-off payments your customer makes in the self-service portals. This article explains how each one works, so you can pick the right setup for your business.
Note: This article covers collecting payments from your customers. To manage the Direct Debit or ACH mandate that pays your own Commusoft subscription, see Managing your Commusoft subscription payment method.
The two ways GoCardless takes payment
GoCardless handles bank-to-bank payments in Commusoft through two separate mechanisms. They are set up in different places and solve different problems, so it helps to know which one you need before you start.
Contract Direct Debit, ACH, and PAD payments
This mechanism collects recurring contract payments automatically. Your customer approves a mandate once, and Commusoft then collects each contract invoice from their bank account.
Best for: service plans and maintenance contracts billed on a schedule
How it starts: your customer approves a mandate request sent during contract setup
Where it lives: the contract template and the Add new contract wizard
Regions: Direct Debit in the UK, ACH in the US, and PAD in Canada
To use it, you need a plan that includes Contracts and the GoCardless integration connected. Your contract template also needs its payment option set to bank payment. See How to take contract payments by Direct Debit, ACH, PAD, or card for the full setup.
One-off portal payments
This mechanism handles single payments your customer makes themselves. They open an invoice or statement in one of the self-service portals, choose to pay by bank, and approve that one payment. Nothing recurring is set up. How the payment is taken depends on your region.
Best for: one-off high value invoice and statement payments, without card fees
How it starts: your customer clicks the portal link in the communication they receive
Where it lives: the invoice and statement portals
Regions: UK, US, and Canada
Pay by Bank in the UK
UK customers paying in GBP use Pay by Bank, a GoCardless feature for instant bank-to-bank payments. Your customer approves the single payment and it is confirmed almost immediately. No mandate is involved.
One-off ACH and PAD payments in the US and Canada
US and Canadian customers pay by ACH or PAD. These schemes need an authorization before money can move, so Commusoft initiates a mandate to take that single payment. Your customer either sets up a new mandate or uses one they have already approved, then confirms the payment.
The payment shows as pending in the portal until GoCardless collects it. Once GoCardless pays out, Commusoft records the payment and the portal shows it as successful. A pending payment is normal, because ACH and PAD payments are not instant.
Bank payments sit alongside card payments in the portal. If you also use the Stripe integration, you can limit card payments above a set amount, so larger invoices are paid by bank instead. See Invoice portal settings to configure this.
How the two compare
Feature | Contract Direct Debit, ACH, and PAD | One-off portal payments |
What it collects | Recurring contract invoices | One-off high value invoice and statement payments |
Who starts each payment | Commusoft collects automatically | Your customer pays in the portal |
Customer approval | One mandate covers all future payments | Each payment is approved individually |
Where it is set up | Contract template and contract wizard | Invoice and statement portal settings |
How it works by region | Direct Debit in the UK, ACH in the US, PAD in Canada, all under a mandate | Pay by Bank in the UK, or a single ACH or PAD payment taken under a mandate in the US and Canada |
How mandates work
A mandate is your customer's authorization to collect payments from their bank account. Mandates apply to every contract payment, and to one-off portal payments in the US and Canada. Pay by Bank payments in the UK do not use them.
When you set up a contract with bank payment, Commusoft emails your customer a mandate approval request. The contract stays in Pending mandate approval status until they complete it. The approval link expires 7 days after it is sent. Once your customer approves it, the mandate becomes active within a couple of working days.
You can reuse a customer's active mandate for future contracts, so they do not need to approve a new one each time. If your customer already has a mandate in GoCardless from before you used Commusoft, you can import it using its mandate reference. Commusoft then manages the payments, and GoCardless cancels any subscriptions it holds.
Note: GoCardless needs an accurate postcode or ZIP code on the customer record to take payments.
Payment timing and references
Bank payments are not instant, so allow for processing time when planning your cash flow. Pay by Bank is the exception, as those payments are confirmed almost immediately.
UK Direct Debit: GoCardless charges your customer around 3 business days after the payment is created, then pays out around 2 business days later
US ACH: GoCardless charges your customer around 1 business day after the payment is created, and you receive the funds around 4 business days after creation
Canada PAD: GoCardless charges your customer around 3 business days after the payment is created, then pays out 3 to 4 business days later
These timings apply to one-off portal payments taken by ACH or PAD as well as to contract payments.
Note: GoCardless sets a maximum transaction amount for each payment scheme. An invoice above that limit is rejected, and any increase is requested from GoCardless directly.
GoCardless generates a reference for every payment. You can search this reference in the GoCardless platform to trace an individual payment.
If a payment fails, Commusoft does not retry it automatically. Send your customer a portal link so they can pay that invoice manually, then check the mandate is still active for future collections.
Common questions
What's the difference between a contract payment and a one-off portal payment?
What's the difference between a contract payment and a one-off portal payment?
The difference is that a contract payment is collected automatically on a schedule under a mandate your customer approves once. A one-off portal payment is a single payment your customer starts and approves themselves in the invoice or statement portal.
Can my US customers pay an invoice in the portal?
Can my US customers pay an invoice in the portal?
Yes, your US customers can pay a single invoice in the portal by ACH, and your Canadian customers can pay by PAD. This is not Pay by Bank, which is only available for customers in the UK paying in GBP. Commusoft initiates a mandate to take the one-off payment, so your customer either sets up a new mandate or uses one they have already approved.
Why does my customer's portal payment show as pending?
Why does my customer's portal payment show as pending?
A portal payment shows as pending because ACH and PAD payments take a few business days to clear. Commusoft records the payment and the portal shows it as successful once GoCardless pays out, so no action is needed while it is pending.
What happens if a contract payment fails?
What happens if a contract payment fails?
If a contract payment fails, Commusoft does not retry it automatically. Send your customer a link to the invoice portal so they can pay manually, and check whether their mandate is still active.
Does this cover the Direct Debit that pays my Commusoft subscription?
Does this cover the Direct Debit that pays my Commusoft subscription?
No, this article does not cover paying your Commusoft subscription. You manage your subscription payment method separately on your billing dashboard. See Managing your Commusoft subscription payment method for that.
Do I need Stripe as well as GoCardless?
Do I need Stripe as well as GoCardless?
No, you do not need Stripe to use GoCardless, but they work well together. GoCardless handles bank payments and Stripe handles card payments. Running both gives your customers a choice, and the invoice portal lets you limit card payments above an amount you set.
