GoCardless integration for recurring payments by direct debit
Pixel builds GoCardless direct debit into custom Laravel platforms, so customers can pay recurring orders from their bank account. We built it for Nourish'd, where it runs alongside card payments on Stripe.
A GoCardless integration lets a custom platform collect recurring payments by direct debit from a customer's bank account. It is for subscription and repeat-order businesses whose customers prefer not to pay by card, or where card fees and expired cards are a real cost. Pixel scopes the build in a fixed-fee Technical Blueprint and quotes it as a fixed price.
Where Direct Debit Fits a Subscription Business
Cards are the default, but they are not always the best way to collect a payment that repeats every week or month.
Cards expire and get replaced
Every expired or reissued card is a failed payment and a customer who has to be chased. A bank account rarely changes.
Some customers will not use a card
Older customers and people paying from a managed budget often prefer, or are required, to pay from a bank account.
Fees add up on repeat orders
On a high volume of recurring payments, the difference between card and direct debit fees becomes a line worth managing.
Two payment methods, one set of rules
Orders, subscriptions and reports should behave the same way whichever method the customer chose.
What a GoCardless integration covers
Mandate setup. At checkout the customer enters their bank details. The platform creates the customer, the bank account and the direct debit mandate in GoCardless, and stores the mandate against the account.
A payment per order. Each time an order is due, the platform creates a payment against the mandate for the exact amount of that order. This suits subscriptions where the amount changes from one cycle to the next.
Status by webhook. Direct debit is not instant. A payment is submitted, then confirmed or failed days later. GoCardless reports each change by webhook, and the platform marks the order paid or failed when it happens.
Cancelled mandates. If a customer cancels the mandate with their bank, or the account is closed, the platform stops trying to collect and cancels the affected order and subscription, so nothing ships unpaid.
Direct debit at Nourish'd
Nourish'd is a meal delivery business with weekly subscriptions. Customers can pay by card through Stripe or by direct debit through GoCardless, and the same subscription engine drives both.
For a direct debit customer, the platform raises a payment against their mandate for that week's order. When GoCardless reports the outcome, the order is updated. The customer's experience, the kitchen's production numbers and the finance reports are the same whichever way the payment was collected.
The integration sits beside the Stripe billing and the CartonCloud fulfilment link in the same platform.
How We Build It
Direct debit events arrive late and sometimes out of order, so the integration is built to check before it acts.
01
Queued events
Each webhook event is queued as its own job, so a burst of events never slows the site.
02
Processed once
Events are recorded as they are handled. A repeated delivery is recognised and skipped.
03
Check current status
Before acting on an event, the job asks GoCardless for the payment's current status, so an old event cannot undo a newer one.
04
Retries
A job that fails is retried several times with increasing delays, from a minute up to an hour.
05
One at a time
A lock per payment stops two events for the same payment being processed at once.
06
Idempotent creation
Customers and payments are created with idempotency keys, so a retry cannot create a duplicate.
GoCardless in production
Nourish'd
A custom meal delivery platform managing subscriptions, funded-care billing, fulfilment, and operational reporting across three customer segments.
30+
Operational Reports
199
Support at Home Providers
3
Customer Segments
GoCardless integration
FAQs
Couldn't find the answer you were looking for? No worries, get in touch with us.
Contact Us
Can GoCardless and Stripe run side by side?
Yes. Customers choose card or direct debit at checkout, and the rest of the platform treats both the same. This is how Nourish'd runs.
How long does a direct debit payment take to confirm?
Several days. A direct debit is submitted to the bank and confirmed or failed later, and GoCardless reports each step by webhook. The platform needs a rule for whether an order ships before or after confirmation, and we agree that with you during scoping.
What happens when a direct debit fails?
The order is marked as failed and the customer is notified. If the mandate itself has been cancelled or the bank account closed, the subscription is cancelled so the platform stops attempting payments that cannot succeed.
Can the payment amount change each time?
Yes. We create a payment per order for the exact amount, so it works for subscriptions where the contents and price change from week to week.
Do you need to rebuild our platform to add GoCardless?
No, provided it is built on Laravel. We add it alongside your existing payment method after auditing how orders and payments currently work.
Find out what adding direct debit to your platform involves
A Technical Blueprint covers how mandates, payments and failures fit into your existing order flow, with a fixed price.
$2,990 inc. GST · credited against your first invoice if you build with us
Related integrations
Stripe integration
Subscriptions, marketplace payouts with Stripe Connect, refunds and failed payment recovery.
Learn more →
CartonCloud integration
Orders sent to your warehouse or delivery partner, with status and tracking sent back.
Learn more →
Klaviyo integration
Server-side events, customer profiles and product feeds sent from your platform to Klaviyo.
Learn more →
All integrations
Every system we connect custom Laravel platforms to.
Learn more →