GoCardless collects payments by bank debit rather than card, which suits recurring billing and subscriptions where card fees and expiry are a problem.
Odoo supports SEPA direct debit natively, but it does not ship a native GoCardless provider, so a GoCardless integration is a custom or third-party build. It is most useful for recurring revenue businesses that want lower fees and fewer failed renewals.
Data Flow
What Data Moves Between GoCardless and Odoo
The integration uses the GoCardless API and webhooks.
Odoo to GoCardless: mandate setup requests and payment collection instructions for invoices and subscriptions.
GoCardless to Odoo: payment confirmations, failures, retries and payouts.
What Goes Wrong
Common Pitfalls
No native module. Plan for a third-party app or a custom build and its maintenance.
Mandate handling. Bank debit needs a customer mandate before collection, which the flow must capture.
Settlement delay. Bank debits take several days to clear, so the payment date and collection date differ.
Failed payments. Debit failures and retries need an accounting and dunning path.
Reconciliation. GoCardless payouts are batched net of fees and must be matched in Accounting.
Setup
How the Integration Is Set Up
Choose the approach: a third-party connector or a custom build.
Create a GoCardless account and obtain API access.
Wire mandate setup into the customer or subscription flow.
Connect payment and payout webhooks.
Map payouts, fees and failed payments to Accounting.
Test mandate, collection and failure flows, then go live.
