GoCardless, ready to run.
The GoCardless integration covers the Direct Debit side of a case. Floowed reads the customer's mandate and their payment history, and cancels, retries or refunds payments when the rules say so.
What it does.
What Floowed reads from GoCardless
- Customers and their mandates
- Payments and their status, including failures
- Refunds and payouts
- Events explaining why a mandate or payment changed
What it writes back
- A retry on a failed payment
- A canceled mandate when a customer offboards
- A refund, where your account allows it
- Metadata on the payment or mandate linking it to the case
The mandate is the thing to watch in GoCardless. An offboarding case that forgets it leaves a live authority to collect. Refunds via the API may need to be enabled on your account before Floowed can issue them, and they are worth routing past a person.
How it connects.
- 1
Connect GoCardless
Using an API key. Nothing migrates and nothing is replaced.
- 2
Build your operation
Describe it in Slack, Teams or the Floowed Dashboard. Floowed builds it and asks only what it can’t work out.
- 3
Let it run
Every case runs from request to outcome, the same way each time, with the reasons on record. Anything sensitive waits for a person.
Questions
Does Floowed integrate with GoCardless?
Yes. It connects with a GoCardless access token, read-only or read-write.
What can Floowed do with GoCardless?
It reads mandates, payments and events, then retries failed payments, cancels mandates or issues refunds as a case requires.
Is my GoCardless data secure?
Floowed only gets the access it needs in GoCardless and never stores a password. A read-only token is enough for cases that only check payment history. Every read and write is logged with the reason.
What does the GoCardless integration cost?
Nothing extra. Integrations are included in every plan, and you only pay for the work your operations do.
Start with GoCardless. Add the rest.
Free to try, no card, no sales call. Your first $80 of credits is on us.