Data Panda brings your GoCardless data together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your team uses every day.
GoCardless was founded in 2011 in London by Hiroki Takeuchi, Tom Blomfield and Matt Robinson, three Oxford graduates who built a developer-friendly way to collect direct debits in the UK. The product expanded into SEPA Core for the eurozone, BACS for the UK, ACH for the United States, PAD for Canada, BECS for Australia and New Zealand, and a Pay-by-Bank flow on top of open banking. The company is authorised by the Financial Conduct Authority under registration 597190, processes around 130 billion dollars in payments a year for roughly 100,000 businesses, and in December 2025 signed an agreement to be acquired by Mollie for 1.05 billion euro.
The reason to pull GoCardless into a warehouse is that bank debit is a different rail than card. A card charge clears in seconds and either succeeds or fails on the spot. A SEPA Core or BACS direct debit collects on a fixed cycle, lands as a payout a few business days later, and can come back as an R-message (rejection, return or refund) up to weeks after capture. Mandate state, collection state, payout state and R-message state all live in GoCardless. Next to your card processor, your subscription tool and your accounting package, that is where you reconcile recurring revenue against what cleared the bank, and where you spot the customer whose mandate failed before the next cycle pulls again.
Mandates, collections and payouts on the same timeline as your card and invoice data.
Let the rest of the stack react to what GoCardless knows about the mandate.
Use GoCardless history to predict the next mandate failure and the next R-message.
Internal tools around the bank-debit data that otherwise lives in the GoCardless dashboard.
A list of concrete reports, automations and AI features we have built on GoCardless data. Pick the one that matches your situation.
Does the GoCardless payout on the bank match the collections behind it?
Each payout is broken down to the collections, fees, refunds and R-message returns that produced it. The gap finance used to chase between the GoCardless dashboard export and the bank statement becomes one reconciled view, with the R-message that caused any mismatch already tagged on the collection it reduced.
Where is the real cost of bank debit lower than card on our subscription book?
Per-collection fee on GoCardless next to the per-charge fee on your card processor, joined on the same customer and the same monthly cycle. On a 500 euro recurring invoice, the SEPA cost typically lands well under one euro while a card fee on the same charge runs into the single-digit-euro range, and the warehouse makes that delta visible per cohort instead of as a vendor-side average.
Which mandates are quietly going to fail at the next cycle?
Mandate-state changes, prior R-message history and collection-success patterns joined per customer. The accounts whose mandate is signalling trouble (a cancellation, a no-account return, a string of insufficient-funds returns) show up before the next cycle pulls and bounces, instead of after the bank reverses the payout.
Every GoCardless payout split to its collections, fees, refunds and R-message returns, next to the bank line and the journal booking. Month-end reconciliation between GoCardless, the ledger and the bank statement stops being a separate cycle on top of the card reconciliation, and the late R-message that lands two weeks after the original payout no longer breaks the close.
For account owners, mandate state and collection history on the CRM record. The customer whose mandate was cancelled three weeks ago shows up on the renewal call instead of three months later in a churn report, and account expansion candidates can be picked from the cohort whose collections clear on the first try.
Collection-success and R-message patterns per scheme, country and bank. The operational call on which markets to push to bank debit and which to keep on card, and which retry policy to use per failure reason, draws on the same warehouse data finance and customer success use, instead of vendor-side averages.
GoCardless payouts land in Exact Online as bank journal entries, with GoCardless fees split out and the underlying collections matched to the invoices they settle. R-message returns post back to the original invoice as a reversal, so the open-invoice list reflects what cleared the bank instead of what was scheduled to clear.
Each Xero invoice paid by direct debit ties to the GoCardless collection that pulled it, and the matching payout lands as a reconciled bank line. Late R-message returns flow back as a reversal on the original Xero invoice, so the receivables ledger no longer carries paid invoices that the bank later reversed.
Each Chargebee subscription is joined to its GoCardless mandate and collection cycle, so a cancelled mandate, a failed collection or a late R-message changes subscription state in the same warehouse view. Customer success sees the recurring revenue at risk on the right cycle, instead of after dunning has already escalated.
Mandate state, last-collection result and recent R-message returns push onto the Salesforce account record as fields and timeline activity. The renewal owner sees a cancelled mandate or a string of insufficient-funds returns on the account before the renewal conversation, instead of finding out from the churn report.
You keep the reporting tool you already have. We connect it to the warehouse where your GoCardless data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
The same schemes GoCardless supports on the merchant side: SEPA Core for the eurozone, BACS for the UK, ACH for the United States, PAD for Canada, BECS for Australia and New Zealand, and the Pay-by-Bank flow on top of open banking. Each scheme has its own collection cycle and its own R-message vocabulary, and the warehouse keeps that distinction so a SEPA insufficient-funds return is not lumped together with a BACS account-closed return.
R-messages (returns, refunds and chargebacks on bank-debit rails) can land days or weeks after the original collection cleared on a payout. The connector keeps the link between the late R-message, the collection it reverses, and the original payout, so finance can post the reversal against the right period without re-opening a closed month-end.
Mollie signed an agreement in December 2025 to acquire GoCardless for around 1.05 billion euro. Until the deal closes and any product or API consolidation is announced, the GoCardless API and the connector keep working as before. We track the post-merger roadmap and will update this page when scheme support, pricing or auth changes for existing customers.
We review your GoCardless setup and the systems around it. Together we pick the first thing worth building.