What the GoCardless API gives you
GoCardless handles Direct Debit and open banking payments. Its API creates mandates, schedules payments, collects variable amounts and reports every change in a payment's status. A custom integration connects all of that to your platform, so billing runs on its own. See the GoCardless API integration guide.
Who it's for
- SaaS and subscription platforms A mandate at sign-up, payments collected on schedule, and access suspended or restored by payment status, with no card expiries to chase. See subscription billing with GoCardless.
- Membership organisations and clubs Fees collected by Direct Debit, renewals automated, price changes applied to existing mandates under the Direct Debit notice rules, and lapsed members flagged.
- Service businesses tired of chasing invoices The invoice amount is collected from the client's bank on the due date, and the payment is marked against the invoice in Xero when it arrives. See GoCardless and Xero.
- Usage-based billing Work out the amount at the end of each period and collect it against the existing mandate.
- Stripe and GoCardless together Card payment at sign-up for instant access, then Direct Debit for the payments after that. See GoCardless vs Stripe.
Why custom rather than a plugin
GoCardless plugins for WooCommerce handle fixed subscription amounts. They don't do variable amounts, controlling access by payment status or matching payments to Xero invoices. A custom build does all three, and you own the code with no extra monthly fees.
What's included
- API keys stored securely on the server, never in the browser
- Webhooks for every payment and mandate event, checked to be genuinely from GoCardless
- Everything tested in the GoCardless sandbox before going live
- A handover document, and the code is yours
Not included: your GoCardless account (it's free, and verification usually takes a few days), the wording of your customer emails (I trigger them, and you own the templates), your Xero subscription, SEPA Direct Debit, and changes to your platform outside the integration.
Payment is 50% to start and the balance on completion. For what drives the price, read what a GoCardless integration costs.
How it's built
- Mandates set up through GoCardless's own pages The customer enters their bank details on a secure GoCardless page or in its embedded flow, not on your site, so you never handle bank details yourself.
- Payments follow Direct Debit timing A Direct Debit payment takes a few working days from being created to being collected, and customers must get advance notice of each payment. The integration works to those rules, so collections happen on the right dates and nobody is surprised by a charge.
- Every status change handled Mandates can be cancelled by the customer at their bank, payments can fail or be charged back, and payouts arrive in batches. Webhooks for all of these are checked to be genuinely from GoCardless, recorded so a repeat is never processed twice, and used to update your platform automatically.
- Failed payments retried sensibly Where a payment fails for lack of funds, it can be retried on a better day, and you're told when one needs a human.
- Safe to retry Requests to create payments are sent with an idempotency key, so a network glitch can never create the same payment twice.
How to get a price
Send a short written spec by WhatsApp, text, email or the form: how you bill, what you're doing by hand now and what your platform is built on. I'll reply within 24 hours with a quote.