PaymentsCustom integration

Holded GoCardless integration

SEPA Direct Debit with GoCardless connected to Holded for frictionless B2B subscriptions.

Request this integration Book a 30-min call

Holded

↔

GoCardless

Implementation time · 5-8 días laborables

Diagnosis

The problem

GoCardless is the most widely used SEPA Direct Debit gateway in Europe for B2B subscriptions and high-value recurring payments. No expired cards, no easy chargebacks, no 2-3% card fees. But its integration with Holded is nonexistent by default. Every signed mandate, every monthly payment, every failed payment stays in the GoCardless dashboard and someone has to replicate it into Holded by hand. For a company with 100+ active B2B subscribers this is chronic admin work that ends up eating away the very advantage of GoCardless (zero churn from expired cards).

Proposal

The solution

Recurring SEPA payments via GoCardless reflected in Holded as recurring invoices with the correct accounting entry. Every mandate signed by a customer, every monthly recurring payment, every failure (insufficient funds, mandate cancelled) and every escalated retry: all in a closed loop with Holded. For companies with B2B subscriptions where SEPA is preferred over card (high amounts, long recurrence), GoCardless is the standard and this integration closes the fiscal loop.

Scope

What we automate

Mandate signed in GoCardless to a Holded contact with SEPA details
Successful recurring payment to a recurring Holded invoice with the correct series
Failed payment to a pending Holded invoice plus a dunning alert
Successful retry after a failure to a paid invoice removed from dunning
Mandate cancelled to an updated customer status in Holded
GoCardless refunds to a Holded credit note with the exact amount
Multi-creditor (several GoCardless accounts) to separate series in Holded
GoCardless fees (1% capped) to an expense entry

Who uses it

Real use cases

These are the profiles that most ask us for the Holded ↔ GoCardless integration and what they get in the end.

Case 01

B2B SaaS with 200 SEPA subscribers

Before: Monthly payments handled manually after each GoCardless notification. 4h/month of admin.

After: Zero-touch recurring invoicing. Admin only manages failures.

Case 02

Professional services firm with a monthly SEPA retainer

Before: Retainers of 2000 to 5000 EUR a month with SEPA entered manually in Holded.

After: Every retainer payment to an automatic recurring invoice. Zero leakage.

Case 03

Advisory firm with monthly client fees

Before: A client with a cancelled mandate kept being invoiced until it was spotted manually.

After: Cancellation propagated immediately to Holded. Zero invoices without coverage.

Before / After

What changes exactly

Without the integration

4h/month replicating GoCardless payments into Holded
Failures handled ad hoc without systematic dunning
Mandate cancelled with no immediate reflection
No CRM integration for churn risk

✓

With the integration

Recurring payments 100% automatic
Escalated dunning with your tool or CRM
Cancellation propagated in real time
Failed payments to a CRM flag for retention

Architecture

How we build it

GoCardless API plus webhooks (mandates, payments, subscriptions, refunds) with HMAC verification. A persisted, idempotent queue keyed on the GoCardless event.id. GoCardless automatic retries (3 escalated attempts) are reflected in Holded with their current status. For failed payments, we integrate with your CRM (HubSpot, Pipedrive) and your dunning tool if you have one (Stunning, Churned).

flow.ts

webhook gocardless.event

→ queue.enqueue(jobId)

→ worker.handle() // idempotent

→ holded.api.call() // retries with backoff

→ log.emit({ status: 'ok' })

FAQ

Frequently asked questions

Does it work with GoCardless Pro and Plus?

Both plans work. Pro has better features for high volumes (Success+, intelligent retries) that we take advantage of. Plus is the standard plan and the base integration is identical.

What about the automatic retries?

GoCardless automatically retries failed payments 3 times with escalation. Each attempt is reflected in Holded as the payment status. When a retry succeeds, the invoice is marked as paid.

SEPA B2B (Business-to-Business)?

Yes. SEPA B2B Direct Debit has a different flow (no refund right for the debtor) and we handle it correctly. B2B mandate signed with double notification, payments with a set term and full traceability.

Multi-creditor (several accounts)?

Yes. If you have several entities collecting via GoCardless (parent company plus subsidiary), each one gets its own series in Holded and separate reporting.

Dunning integrated with the CRM?

Yes. Failed payments send a flag to HubSpot/Pipedrive as a churn risk. If you use a dedicated tool (Stunning, Churned) we connect that too.

How long does it take?

Between 5 and 8 business days. Multi-creditor or dunning with a CRM can add 3 to 4 days.

We also build

Related integrations

See catalog

Payments

Shall we talk about your GoCardless integration?

A 30-minute call, no strings. You leave with scope and a price.

I want this integration See all integrations