Payments
GoCardless
Collection runs and failures reflected against the customer's open items.
Where this actually stands
PlannedPlanned
Designed and on the roadmap: we know what it would do and roughly what it takes. No code has been written, and we are not going to imply otherwise.
Connection type
API
A direct connection to the other system's interface, reading and writing on a schedule or on an event.
What it would do
GoCardless, connected.
Direct debit collections matched to invoices.
G1 does not ask you to replace a system that works. Where a connection exists, the point of it is to remove the person in the middle — the weekly export, the re-key, the spreadsheet that reconciles two tools that should have agreed in the first place.
Payment providers settle in batches and charge fees on the way. Connecting them means receipts match invoices and fees post where they belong.
Every categoryModules it feeds
- Accounts receivableAvailableInvoices out, cash in, and a clear view of who owes what.
- Cash flowAvailableBank feeds in, reconciliation done, cash position you can trust.
A connector is only as useful as the module reading it. Where the module is still in development, the connector waits for it.
Payments
Others in the same category.
- On requestExplore
API
Stripe
Settlements, fees and refunds posted correctly.
- PlannedExplore
File import
PayPal
Batch settlement reconciled to receipts.
- On requestExplore
File import
Adyen
Multi-currency settlement, reconciled.
Names listed here are trademarks of their respective owners and appear only to describe compatibility and connection plans. No partnership, endorsement or affiliation is implied, and no third-party logos are used anywhere on this site.
Connect what you already use
Tell us how GoCardless is used where you are.
What matters is not the connector — it is the work it removes. Describe the manual step and we will tell you whether a connection actually fixes it.