Data Panda brings your Twikey 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.
Twikey is a Belgian payment platform specialising in SEPA direct debit, digital mandates and recurring payments. It connects to more than three and a half thousand banks across Europe and handles both SEPA Core and SEPA B2B mandates, plus UK BACS, making it the backbone a lot of Benelux SaaS and utility companies use for subscription collection.
The point of pulling Twikey into a warehouse is that a failed direct debit is almost always a churn signal, not a technical retry. Mandate-level data, collection attempts, failure reasons and refund events sit outside the accounting system by design. Next to CRM, billing and support, the Twikey stream turns into the earliest and most honest churn indicator most subscription businesses have, instead of an email from the accountant next month.
Mandate activity, collection success and refund volume next to revenue and CRM stage.
Let a Twikey event fire actions everywhere it matters.
Use collection history to score churn and optimise retry logic.
Internal tools on Twikey data for people who do not need the Twikey UI.
A list of concrete reports, automations and AI features we have built on Twikey data. Pick the one that matches your situation.
Which customers are signalling churn through their direct debit?
Customers whose last collection failed, whose mandate was refused or who cancelled the mandate themselves, ranked by annual contract value. The list reaches CS days before the customer writes to cancel, not weeks after.
How much recurring revenue arrives as recurring revenue?
Billed recurring revenue against the amount collected, per segment and month, with refunds and reversals taken out. Exposes the gap between what billing thinks is recurring and what the bank delivered.
Which retry strategy is recovering revenue?
Recovery rate per retry window, per failure reason and per country. Separates the retries that are genuinely saving subscriptions from the retries that only delay a customer deciding to cancel.
Recurring revenue reconciled against what the bank cleared, with refunds and reversals tied back to the invoice. Month-end stops hunting for variance between billing, Twikey and the bank.
Mandate state and collection success visible on the CRM record. A renewal conversation sees the customer whose card expired or whose mandate refused twice, before that customer writes to cancel.
Failure-reason mix, retry effectiveness and country-level success on one board. Payment-operations decisions move from 'retry all' to a policy shaped by what recovers revenue.
Twikey collection successes, failures and refunds post into Exact Online as bank and adjustment entries, matched to the invoice they settle. The Belgian accounting close stops waiting on a SEPA batch export from Twikey and works against live events.
Dutch entities running Yuki receive their Twikey collection state with invoice match and VAT handling. The Yuki open-items screen reflects what the direct debit delivered, not what was optimistically expected.
Outgoing Billit invoices are linked to the matching Twikey mandate and collection attempt. The Billit receivables screen shows which invoices are covered by a live mandate, which ones are waiting on collection and which ones became a churn signal.
For subscription businesses running SEPA through Twikey and card through Stripe, success rate, recovery rate and per-rail cost land in the same warehouse. Pricing and rail-selection decisions move from vendor claims to blended outcome per customer segment.
These are the 3 tables we currently pull from Twikey into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.
Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.
You keep the reporting tool you already have. We connect it to the warehouse where your Twikey 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.
Yes. All mandate types Twikey supports land in the warehouse as first-class records with creation, amendment and cancellation history. Collection attempts carry the rail, country and failure reason so retry and dunning analysis can be done per mandate type.
Yes. The SEPA pain responses are kept verbatim alongside Twikey's own event model. Finance can reconcile down to the bank response code when a collection failed, which is the level of detail auditors and compliance teams look for.
We review your Twikey setup and the systems around it. Together we pick the first thing worth building.