Skip to content
Register

Payment integration

Collect direct debit payments with GoCardless

The GoCardless integration lets you collect Invoice Crowd invoices, including supported recurring payments, by direct debit from your customer's bank account. Invoice Crowd records each payment after GoCardless confirms it, and can send refunds back through GoCardless.

Review the flow All integrations
  • Status: Active direct debit
  • Checked against the app
  • Provider terms still apply
Invoice Crowd Payment Methods with GoCardless selected and a GoCardless account set to Live, a paid invoice recorded after GoCardless confirmed it, and the Refund window sending money back via GoCardless.

From setup to paid

How GoCardless fits the Invoice Crowd payment boundary

Connection, customer checkout and final settlement are separate stages. Read the status and limitations before showing the method on a live invoice.

Connect the merchant account

Each business profile has its own account and live or test mode.

Invoice Crowd GoCardless account form with Live and Sandbox modes and a fictional nickname, the business's GoCardless accounts, and the Access Token kept write-only when editing.

Enter only the fields the provider requires

GoCardless API credentials, mode and an enabled direct-debit account for the selected business.

  • Selected business profile
  • Explicit live or test mode
  • Write-only secret editing

Check the provider accepts your business first

Scheme, country, currency, collection timing and merchant availability are controlled by GoCardless.

  • Merchant country and account
  • Invoice and settlement currency
  • Provider fees and review

Understand the customer path

The payment option only shows when it can be used for that invoice.

Invoice Crowd invoice INV-2048 for Atlas Legal LLP in GBP, the customer's Select a Payment Method sheet with Pay Using GoCardless, and what GoCardless asks for next.

Use the one-time payment flow

The active direct-debit path creates billing requests and mandates tied to your business and that customer, then waits for GoCardless to confirm before recording payment.

  • The amount comes from the invoice
  • The payment is applied to that invoice
  • The customer pays on the provider's own page

Recurring payments work differently

Recurring direct-debit handling is active through exact customer, mandate, subscription and payment bindings.

  • One-time and recurring differ
  • Some existing setups only keep running
  • New ones aren't offered where unsupported

Checked before the payment is recorded

An invoice is marked paid only when the provider confirms it.

Invoice Crowd Payments Needing Review holding a GoCardless payment for INV-2048 that arrived after the invoice was paid, with the checks GoCardless payments must pass before they are recorded.

The payment must match the invoice

Authenticated provider read, exact payment, customer and mandate, invoice/subscription metadata, amount, currency and confirmed or paid-out state.

  • Merchant account and mode
  • Same invoice, amount and currency
  • The provider reports it as paid

Know the current limits

A pending direct debit remains pending locally; a browser response or unverified callback cannot mark it paid.

  • Nothing is assumed paid
  • Pending stays pending
  • Mismatches are refused

Integration facts

What to verify before using GoCardless

The fields below describe the current Invoice Crowd path; the provider remains the source for merchant eligibility, fees and regional availability.

  • Availability

    Active direct debit

  • One-time payment

    The active direct-debit path creates billing requests and mandates tied to your business and that customer, then waits for GoCardless to confirm before recording payment.

  • Recurring payments

    Recurring direct-debit handling is active through exact customer, mandate, subscription and payment bindings.

  • Merchant setup

    GoCardless API credentials, mode and an enabled direct-debit account for the selected business.

  • Settlement evidence

    Authenticated provider read, exact payment, customer and mandate, invoice/subscription metadata, amount, currency and confirmed or paid-out state.

  • Regional fit

    Scheme, country, currency, collection timing and merchant availability are controlled by GoCardless.

  • Current limits

    A pending direct debit remains pending locally; a browser response or unverified callback cannot mark it paid.

  • Invoice data

    Amount, currency and allocation are derived from the current server-side invoice state.

  • Unmatched payments

    If a confirmed GoCardless payment can't be applied to its invoice, for example because the balance changed after checkout started, Invoice Crowd holds it in Payments Needing Review. You then apply it to the invoice, keep it as customer credit, or refund it.

  • Refunds

    Choose Refund on the invoice in Invoice Crowd and the money goes back to the customer through GoCardless. The refund is booked only after GoCardless confirms it. This covers online payments made on the invoice page.

  • Provider fees

    Gateway fees, exchange costs and settlement timing come from the merchant agreement, not the Invoice Crowd subscription.

  • Alternative gateways

    Configure another active provider when this gateway does not support the merchant, customer, currency or collection model.

Questions

GoCardless and Invoice Crowd, answered

Is the GoCardless integration currently available in Invoice Crowd?

Yes. GoCardless direct debit is active in Invoice Crowd. It sets up a billing request and mandate for your customer, then waits for GoCardless to confirm the payment before recording it.

What do I need to connect GoCardless?

GoCardless API credentials, mode and an enabled direct-debit account for the selected business. Scheme, country, currency, collection timing and merchant availability are controlled by GoCardless. GoCardless needs a paid Invoice Crowd plan; the free plan includes PayPal.

How does GoCardless one-time checkout work?

The active direct-debit path creates billing requests and mandates tied to your business and that customer, then waits for GoCardless to confirm before recording payment.

Does GoCardless support recurring payments in Invoice Crowd?

Recurring direct-debit handling is active through exact customer, mandate, subscription and payment bindings.

How does Invoice Crowd decide that a payment succeeded?

Authenticated provider read, exact payment, customer and mandate, invoice/subscription metadata, amount, currency and confirmed or paid-out state. A browser return or posted status alone cannot settle the invoice. A confirmed payment that can't be applied to its invoice is held in Payments Needing Review until you decide what to do with it.

Are gateway fees included in Invoice Crowd pricing?

No. Provider transaction fees, foreign-exchange costs, settlement timing and account terms are controlled by the gateway and merchant agreement. Check the provider before activation.

Can I refund a GoCardless payment from Invoice Crowd?

Yes. Choose Refund on the invoice (from the invoice list, the editor or Manage Payments), then pick "Refund it to the customer via GoCardless". Invoice Crowd sends the refund through GoCardless and books it only after GoCardless confirms it. This works for online payments made on the invoice page, not for recurring, subscription or payment-link invoices.

Test GoCardless with a representative invoice

Start with sandbox or test mode where the provider offers it, verify the exact currency and payment result, then plan production activation.

  • Never marked paid from the browser alone
  • Provider terms apply
  • Current status is visible
Start free Payment gateway overview