Accounting

GoCardless + StackGo

Run compliance from inside GoCardless. Checks start from a record and the result lands back on the client.

GoCardless publishes 10 trigger events and 15 actions on its public Zapier listing. That is what a StackGo connector would be built on.

Accounting System of record Not connected yet
What GoCardless is

GoCardless is a payments platform helping businesses collect payments directly from customer bank accounts.

Description supplied by GoCardless.

The trigger

What starts a check

You do not open StackGo. A change in the system starts the work, and the system stays your source of truth.

EventWhat StackGo doesWhat comes back
A new contact or customer is createdStarts identity collectionVerification status
A designated service is addedRuns the checks that service requiresResult and risk rating
Ownership or details changeRe-screens the related partiesUpdated status
The write-back

What StackGo puts back on the record

A GoCardless connector would write named fields onto the record, not a link to a portal. These are the fields StackGo writes on the systems it connects to today.

  • Verification status
  • Risk rating
  • Last checked
  • Report link
  • Verified name
  • Date of birth
  • Document checked
  • Screening result
  • Beneficial owners
  • Form responses
  • Verification report (PDF)

Every field is optional. What each one holds, and which carry personal data, is set out once in what “integrates with” actually means.

Everything else GoCardless publishes

GoCardless’s public integration surface

The rest of what GoCardless exposes on Zapier, beyond the workflow. This is the raw material a connector would use.

10 events
  • New Payment Authorisation Request
  • Payment Authorisation Approved
  • Mandate Activated
  • Mandate Cancelled
  • New Mandate Created
  • Payment Confirmed
  • Failed Payment
  • Payment Paid Out
  • Payment Submitted
  • Payout Paid
15 actions
  • Create Mandate Authorisation Request
  • Create Instant Bank Payment
  • Create Instant First Payment + Direct Debit Mandate
  • Create Direct Debit Payment
  • Create Subscription
  • Custom Actions (Beta)
  • API Request (Beta)
  • Search for a Billing Request
  • Search for a Customer
  • Search for a Customer Bank Account
  • Search for a Mandate
  • Search for a Payment
  • Search for a Payout
  • Search for Payout Items by Payout ID
  • Fetch Custom Actions

Names are GoCardless’s own, read from its public Zapier listing on 28 August 2026.

Questions

Common questions about GoCardless

How to integrate GoCardless?

There is no StackGo connector for GoCardless yet. GoCardless publishes 10 trigger events and 15 actions through Zapier, so building one is realistic. Requests decide the build order.

What is GoCardless used for?

GoCardless is a payments platform helping businesses collect payments directly from customer bank accounts.

Questions taken from what people actually search in Australia. We answer only the ones our own data answers.

Where this sits

GoCardless is the record. StackGo runs the steps around it.

Every step writes back to GoCardless, so the client record stays the source of truth.

Want GoCardless connected?

Requests decide the build order. Tell us and we will tell you where it sits.

Request this integration

Ready to make onboarding minutes, not hours?

Start free and run your first check today, or book a demo and we will walk you through it.