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
Payment integration
Connect GoCardless without treating checkout as proof
Use GoCardless mandates for eligible direct-debit invoice and recurring payments in Invoice Crowd, with provider state verified before settlement.
- Status: Active direct debit
- Verified against application docs
- Provider terms still apply
Last updated:
Configuration to settlement
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
Credentials and mode stay tied to the selected business.
Confirm provider eligibility before rollout
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
Availability is evaluated before a customer enters checkout.
Use the supported one-time flow
The active direct-debit path creates tenant/customer-bound billing requests and mandates, then waits for confirmed provider state before recording payment.
- Server-owned amount
- Bound invoice allocation
- Provider-controlled payment step
Read the recurring-payment boundary separately
Recurring direct-debit handling is active through exact customer, mandate, subscription and payment bindings.
- One-time and recurring differ
- Existing bindings may be compatibility-only
- Retired creators stay unavailable
Verify before recording money
The final local state follows provider evidence, not the browser.
Match the commercial record exactly
Authenticated provider read, exact payment, customer and mandate, invoice/subscription metadata, amount, currency and confirmed or paid-out state.
- Merchant account and mode
- Allocation, amount and currency
- Successful provider state
Keep the current limitation visible
A pending direct debit remains pending locally; a browser response or unverified callback cannot mark it paid.
- No inferred settlement
- Pending stays pending
- Mismatch fails closed
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 tenant/customer-bound billing requests and mandates, then waits for confirmed provider state 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 boundary
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.
-
Customer result
A provider screen or browser return is a locator, not sufficient settlement proof.
-
Retries
Durable attempts and stable provider identities prevent an uncertain response from becoming an unbounded duplicate payment.
-
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?
Current status: Active direct debit. The active direct-debit path creates tenant/customer-bound billing requests and mandates, then waits for confirmed provider state before recording payment.
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.
How does GoCardless one-time checkout work?
The active direct-debit path creates tenant/customer-bound billing requests and mandates, then waits for confirmed provider state 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.
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.
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.
- No browser-only settlement
- Provider terms apply
- Current status is visible