GoCardless payment method is a bank debit option built by GoCardless, a London fintech started in 2011, focused on collecting payments from customer bank accounts through direct debit schemes and similar rails.
Merchants add it when they want a reliable way to collect one-time and recurring payments without relying only on cards, especially for invoicing and subscriptions.
It’s often offered alongside cards, wallets, and local bank methods. Once you have that mix, the hard part is not adding another button. It’s keeping operations clean across different providers, statuses, and reports. Akurateco helps by giving teams one place to manage payments, track approval performance, and keep reporting consistent across the full checkout.
What is GoCardless?
GoCardless is a payment service that lets merchants collect bank debit payments after the customer gives authorization. In practice, the GoCardless payment gateway sits between your product and local bank debit schemes, handling the mandate, payment initiation, and status updates.
It’s commonly used by subscription businesses, SaaS, service companies, and marketplaces that want predictable collections for invoices, memberships, and recurring billing, where bank debit is a natural fit.
Where GoCardless is used
GoCardless is most common in markets where bank debit schemes are widely used for consumer and business payments. Coverage includes the United Kingdom and the Eurozone, and it also supports collections in the United States, Australia, New Zealand, Canada, Sweden, and Denmark.
You will often see it in subscriptions and membership models, SaaS billing, professional services, and B2B invoicing, where customers prefer paying from a bank account instead of a card.
How GoCardless works
- The customer selects GoCardless at checkout or during account setup and is shown an authorization form to approve bank debit payments.
- Your system creates a mandate request using the GoCardless API and receives a mandate reference once the customer submits their details.
- After the mandate is active, you submit a payment request that references that mandate, either for a one-time payment or a scheduled recurring charge.
- GoCardless sends the payment instruction through the relevant scheme, such as Bacs in the UK, SEPA in Europe, ACH in the US, or local schemes in other supported regions.
- The payment moves through scheme processing, so it can sit in a pending state before it reaches a final outcome.
- Your system receives status updates through callbacks or webhooks, so the order or invoice stays in sync with the final result.
- You fulfill the order or mark the invoice as paid when confirmation is final, and handle failures using your standard retry or customer outreach process.
- Finance reconciles payouts using scheme and payment references from reports, then matches them back to invoices and customer records.
Merchant requirements and setup basics
Common requirements for GoCardless integration:
- Merchant onboarding and account verification, plus a payout bank account that matches the scheme and currency you plan to use
- A clear plan for collecting customer authorization, including mandate language and consent capture
- GoCardless API credentials and a webhook endpoint to receive payment, mandate, and refund events
- A way to handle pending and failed states in your order, invoice, or subscription logic
- Testing in a sandbox environment before launch, including success, failure, and cancellation scenarios
- A simple internal check of which GoCardless supported countries apply to your account, since access can depend on scheme enablement and onboarding details
Fees, settlement, and refunds overview
GoCardless fees are typically defined in your agreement and can vary by region, scheme, sales channel, and your business profile. Some teams also see different pricing for domestic versus cross-border collections, or for optional services tied to FX and payout handling.
GoCardless settlement depends on the bank debit scheme and your payout schedule, so timelines are usually measured in business days rather than seconds. Approval and payout are related, but not the same event.
GoCardless refunds are generally supported, but the exact behavior and timing can depend on the local scheme rules and how far the payment is in the processing lifecycle. Support teams usually do best when they track refund status to completion and reconcile it to the original payment reference in reports.
Pros and cons of GoCardless for merchants
Pros:
- Strong fit for subscriptions, memberships, and invoice collections where paying from a bank account is normal
- Once a mandate is in place, repeat payments can feel simpler for customers than re-entering card details
- Helps reduce disruptions tied to card expiry and card reissues for recurring billing
- Useful for higher value payments where bank debit is preferred over cards in some markets
Cons:
- Bank debit confirmation is not always instant, so you need clean handling for pending outcomes
- Customer adoption depends on familiarity with local bank debit schemes, which can vary by region
- Returns and disputes follow the scheme rules, and resolution can take longer than a card authorization flow
Using GoCardless in a multi-method checkout
GoCardless is rarely a standalone choice. Many teams keep cards for broad coverage, then add bank debit for customers who prefer paying from a bank account, especially for subscriptions and invoicing. In some segments, offering both can reduce churn because customers can switch to a more stable payment option when cards fail.
Once you accept GoCardless alongside other methods, operational work grows fast: different dashboards, different event models, and different reporting cutoffs. A payment orchestration platform helps by keeping payment monitoring and reporting in one place, so teams can compare performance across methods, investigate declines, and keep finance reconciliation consistent without stitching together multiple admin panels.
Integration via Akurateco
Akurateco helps teams expand payment coverage with one orchestration layer across multiple payment methods. If a specific payment method is required for your use case, we can enable it upon request. Reach out to confirm options.
FAQ about GoCardless
What is GoCardless?
GoCardless is a bank debit payment method that lets businesses collect payments from customers’ bank accounts after the customer authorizes a mandate. It is widely used for invoices and recurring billing, where bank debit is a natural alternative to cards.
Where is GoCardless available?
GoCardless supported countries include the United Kingdom and the Eurozone, and it also supports collections in the United States, Australia, New Zealand, Canada, Sweden, and Denmark. Exact availability can depend on which schemes your account can use, so teams usually confirm the supported countries during onboarding as a quick operational check.
Does GoCardless support refunds?
Yes, GoCardless refunds are generally possible. What matters in practice is timing and scheme rules, so teams track the refund until it reaches a final status and then reconcile it back to the original payment reference in reporting.
How long does the settlement take?
GoCardless settlement depends on the local bank debit scheme and your configured payout schedule, so it is typically not instant. A payment can be confirmed for the customer, while the payout arrives later according to banking cutoffs and reporting cycles.
Is GoCardless good for subscriptions or recurring?
Often yes, but it depends on your market and customer preference. Many subscription teams like bank debit because it avoids card expiry issues, but you still need a clear plan for failed payments, retries, and customer communications. In multi-provider setups, unified reporting matters so finance and support can trace every renewal attempt without jumping between systems.
Can I offer GoCardless alongside cards and other local methods?
Yes, many merchants do exactly that, especially when they serve multiple regions or customer segments. The main challenge is operations, not the checkout button, and that is where payment orchestration matters. With orchestration, teams get one view of payment status, performance, and reports across methods, so issues are easier to investigate and reconcile.
