Skip to main content
All CollectionsApps, Tools & Integrations
Using the Go Cardless integration
Using the Go Cardless integration

This integration lets you manage Direct Debit mandates from The Layer

Written by Raymond Carrel
Updated over a week ago

The Layer’s integration with Go Cardless offers a way of managing Direct Debit Mandates directly from the Customer record.

Using this functionality reduces the administration time for Mandate creation, or cancellation, and provides a view of all Mandate statuses.

What is possible?

  • Sync of existing Go Cardless customers – where the record already exists, this can be directly linked to the Customer record in The Layer.

  • Unlinking Customer records – where information has changed and the record should no longer be connected to Go Cardless, this link can be broken from within the Customer record.

  • Creation of Customer records in Go Cardless – where the Customer record does not currently exist, the Billing request process will capture the relevant information to create the record in Go Cardless.

  • Mandate management:

    • Creation of Mandates – links for Mandate creation can be sent from the Customer record, or from the quote using the Billing Requests feature. This allows the Customer to set up the Mandate directly with Go Cardless

    • Mandate visibility at a Customer or Company level – Mandate statuses can be viewed from the Customer record, or all Mandates viewed at a Company level.

    • Cancellation of Mandates – simple cancellation process directly from the Mandate record in The Layer.

How does this work?

A Billing Request is a way of sending information from The Layer to Go Cardless for processing. Using this flow, a request for Direct Debit information is sent to your Customer by email. The Customer is able to follow the link and input the information required to set up a Mandate in Go Cardless.

Once a Billing Request has been sent from The Layer, it will progress through from ‘Pending’ – where it is awaiting action, to ‘Fulfilled’ where all information has been captured and the Mandate has been created. For security reasons, a Billing Request has a limited validity period, however, it is possible to extend this as required. If necessary, a Billing Request can be Voided in The Layer prior to progression to ‘Fulfilled’. Fulfilled Billing Requests are considered completed and cannot be voided.


It is not possible to sync Lead records with Go Cardless.


Managing Existing Go Cardless customers

Where a Customer record is already present in Go Cardless, this can be synchronised to The Layer using the ‘Sync Customer’ option from the ‘Go Cardless’ menu in the Customer record.

The Customer record is then selected from the drop down list.

Once completed, any associated Mandates will be visible from the ‘View all Mandates’ menu option.

Creating a new Go Cardless Customer

Where a Customer record does not exist in Go Cardless, this can be created from within The Layer.

As explained in the previous section, select ‘Sync Customer’ option from the ‘Go Cardless’ menu in the Customer record. Do not select a record from the drop down, this should be left blank and this will enable the creation of a new record.

Requesting a new Mandate using the Billing Request flow

A Mandate can be requested either at a Quotation level or a Customer level.

To create a Billing Request from a Quotation, select ‘Create Billing Request’ from the ‘Operations’ menu in the quotation builder.

To create a Billing Request from the Customer record, select the ‘Create Billing Request’ option from the ‘Go Cardless’ menu in the Customer record.

An advisory message will appear if any Billing Requests already exist. Continue with the request and, once complete, the following screen will appear. It is now possible to email the link to the customer by clicking on ‘Email DD Link’.

Resending the DD link

To resend the DD link to the Customer at a later date, select ‘View Billing Requests’ from the ‘Go Cardless’ menu.

From here, it is possible to either copy the DD link (‘Direct Debit Link’ button) or create an email (‘Email DD Link’ button).

If selecting ‘Direct Debit Link’, this copies the link to the clipboard ready for inserting into an email or other document.

If selecting ‘Email DD Link’, this will open the email in a new window and this will later show in Tasks (once sent). Note: the email can be edited before sending, if required.

Voiding a Billing Request

It is possible to void a Billing Request up until the point its status updates to ‘Fulfilled’. At this point, the request process is considered complete.

To void the request, select ‘Void’ against the required record.

Extending a Billing Request

Billing Requests are valid for 7 days from the point of creation. It is possible to extend the date by selecting ‘Extend Expiry’ against the required request. The Expiry date will update to 7 days from that moment.

Creation of the Mandate

When the Direct Debit link has been completed, this will create a Mandate in Go Cardless. Mandates can be viewed from both the Global Operations view and the Customer view, as explained in the section below.

Visibility of Billing Requests and Mandates.

It is possible to view Billing Requests and Mandates at either a Customer level or via the Global Operations view, which will show ALL Customers.

From within a Customer record, select the required option from the ‘Go Cardless’ menu.

The status of the Mandate is taken from Go Cardless and will update automatically as it changes in Go Cardless.

The Global Operations menu is accessible via the ‘Operations’ link

Cancellation of the Mandate

Mandates can be cancelled directly from The Layer.

To cancel a Mandate, select the ‘Cancel’ option against the required record. A confirmation screen will show this as complete.

Printing a copy of the Mandate

A PDF view of the Mandate can be accessed from the Mandate record.

Unlinking a Customer record

If a Customer record no longer needs to be linked to the Go Cardless record, it can be unlinked by selecting ‘Unlink Customer’ from the ‘Go Cardless’ menu.

Did this answer your question?