Crezco connector

Use your Crezco data for reporting, automation and AI.

Data Panda brings your Crezco 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.

Crezco

About Crezco

Pay-by-bank over open banking, embedded in invoices and payouts.

Crezco is a London-based payments API for account-to-account transfers built on UK and EU open banking. The company (Crezco Limited, Companies House 11752182, incorporated January 2019) is authorised by the UK Financial Conduct Authority as an Electronic Money Institution under firm reference 1027543, and runs cross-border flows on top of Currencycloud. Platforms and software vendors embed the Crezco API to collect payments on invoices, push out payouts to suppliers and contractors, and run payroll and expenses, all over real-time bank rails instead of card.

The reason to pull Crezco into a warehouse is that pay-by-bank is a different rail than card. A card charge clears in seconds and either succeeds or fails on the spot. A Crezco payment request sits open until the payer authenticates with their bank, the payment leaves an account, the bank-provider responds, and the payout lands. Payment-request state, payment state, payout state and bank-provider behaviour all live in Crezco, alongside the customer and the mandate. Next to your card processor, your subscription tool and your accounting package, that is where you reconcile pay-by-bank revenue against what cleared the bank, and where you spot the payment request that expired before the payer ever opened it.

What your Crezco data is for

What you get once Crezco is connected.

Pay-by-bank revenue, not a separate dashboard

Payment requests, payments and payouts on the same timeline as your card and invoice data.

Payment-request conversion from created to paid by bank-provider and country
Payout reconciliation broken down to the underlying payments and refunds
Pay-by-bank cost per transaction next to card and SEPA on the same checkout

Bank-provider-aware automation

Let the rest of the stack react to what Crezco knows about the payment request.

Paid payment request settles the matching invoice in the ledger
Expired payment request triggers a follow-up reminder before write-off
Failed payout opens an investigation task with the bank-provider context attached

AI workflows

Use Crezco history to predict which payment requests pay and which expire.

Conversion scoring per bank-provider, country and customer cohort
Best-time-to-send models trained on your own payment-request history
Payout-failure prediction from prior bank-provider response patterns

Custom apps on your data

Internal tools around the pay-by-bank data that otherwise lives in the Crezco dashboard.

Payment-request follow-up board for the AR team
Payout reconciliation app across Crezco, card and bank
Customer payment-history lookup for support agents

Use cases

Use cases we deliver with Crezco data.

A list of concrete reports, automations and AI features we have built on Crezco data. Pick the one that matches your situation.

Payment-request conversionCreated, opened, paid and expired payment requests by bank-provider and country.

Payout reconciliationCrezco payout tied back to the payments, refunds and fees that produced it.

Pay-by-bank vs. card costPer-transaction Crezco cost on the same invoice next to the card fee on your processor.

Bank-provider performanceConversion and time-to-pay per bank-provider, so you see which banks slow checkout.

Country and currency mixUK and EU payment volume, currency and bank-provider split on one timeline.

Expired-request follow-upOpen payment requests grouped by age, customer and amount for AR follow-up.

Mandate-driven recurringActive mandates and the recurring payments they pulled, by customer and frequency.

Time-to-pay distributionHours from payment-request created to bank settlement, per bank-provider and country.

Payout failure baselineFailed payouts by reason and bank-provider, so an outlier supplier stands out.

Refund and reversal volumeRefunds out of Crezco split per reason and tied to the original payment.

Real business questions

Answers you will finally get.

Does the Crezco payout on the bank match the payments behind it?

Each Crezco payout is broken down to the payments, fees and refunds that produced it. The gap finance used to chase between the Crezco dashboard export and the bank statement becomes one reconciled view, with the refund or failed payment that caused any mismatch already tagged on the customer it came from.

Which bank-providers are quietly killing pay-by-bank conversion?

Created-versus-paid rates per bank-provider, joined to country and customer cohort. The banks where payers drop off in the auth flow show up next to the banks where the payment request lands in seconds, so you can decide where to nudge customers toward a different rail instead of guessing from a single funnel number.

Where is pay-by-bank cheaper than card on our invoice book?

Per-transaction Crezco cost next to the per-charge fee on your card processor, joined on the same invoice and the same customer. The warehouse makes that delta visible per cohort instead of as a vendor-side average, so the choice between card and bank stops being a gut call and starts being a number per customer segment.

Value for everyone in the organisation

Where each function gets value.

For finance leaders

Every Crezco payout split to its payments, fees and refunds, next to the bank line and the journal booking. Month-end reconciliation between Crezco, the ledger and the bank statement stops being a separate cycle on top of the card reconciliation, and the late refund that lands days after the original payout no longer breaks the close.

For sales leaders

For account owners, payment-request status and pay-by-bank history on the CRM record. The customer who left three payment requests to expire shows up on the next renewal call instead of three months later in a churn report, and the customers who pay on the first request are visible as expansion candidates.

For operations

Conversion and time-to-pay per bank-provider, country and customer cohort. The operational call on which markets to push to pay-by-bank and which to keep on card, and which bank-providers need a different checkout copy, draws on the same warehouse data finance and customer success use, instead of vendor-side averages.

Ideas

What you can automate with Crezco.

Crezco

Pair with Xero

Reconcile Crezco payments in Xero

Each Xero invoice paid through a Crezco payment request ties to the underlying payment and the matching payout lands as a reconciled bank line. Refunds out of Crezco flow back as a credit note on the original Xero invoice, so the receivables ledger reflects what cleared the bank instead of what was scheduled to clear.

Crezco

Pair with QuickBooks Online

Post Crezco payouts into QuickBooks Online

Crezco payouts land in QuickBooks Online as bank deposit entries, with Crezco fees split out and the underlying payments matched to the invoices they settle. Failed payouts and refunds post back to the original invoice, so the open-invoice list in QuickBooks reflects bank-cleared cash instead of optimistic settlement.

Crezco

Pair with Exact Online

Settle Exact Online invoices on Crezco payment

When a Crezco payment request on an Exact Online invoice is paid, the invoice is marked settled in Exact, the bank journal entry is created, and the Crezco fee is posted to the right cost account. Expired payment requests trigger an AR-follow-up flag on the original invoice instead of a manual review at month-end.

Crezco

Pair with HubSpot

Surface Crezco payment status on the HubSpot record

Payment-request status, time-to-pay and recent refund activity push onto the HubSpot company and contact record as properties and timeline activity. The renewal owner sees a string of expired requests on the customer before the renewal conversation, and a clean payer cohort surfaces as expansion candidates instead of being buried in the Crezco dashboard.

Crezco

Pair with Slack

Alert finance in Slack on payout exceptions

Failed Crezco payouts, mismatches between payout and underlying payments, and large refunds drop into a finance Slack channel with the customer, the bank-provider and the original payment-request link attached. The team handles the exception in minutes instead of finding it during the next reconciliation cycle.

Crezco

Pair with monday.com

Track payment-request follow-up in monday.com

Open payment requests beyond their expected pay window create or update a follow-up item in monday.com, grouped by customer and amount, with the bank-provider history attached. AR works through one prioritised board instead of digging through the Crezco dashboard for stragglers.

Your existing tools

Your data lands in a warehouse. Your BI tools read from it.

You keep the reporting tool you already have. We connect it to the warehouse where your Crezco data lives.

Power BI Microsoft

Fabric Microsoft

Snowflake Data warehouse

BigQuery Google

Tableau Visualisation

Excel Sheets & pivots

Three steps

From Crezco to answers in three steps.

Connect securely

OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.

Land in your warehouse

Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.

Reporting, automation, AI

We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.

Two ways to work with us

Pick the track that fits how you work.

Track 01

Self-serve

We set up the foundation. Your team builds on top.

Crezco connector configured and running
Warehouse set up in your cloud account
Clean access for your Power BI, Fabric or Tableau team
Documentation on what's in the data model
Sync monitoring so you're warned before reports break

Best fit Teams that already have a BI analyst or data engineer and want to own the build.

Track 02

Done for you

We build the whole thing, end to end.

Everything in Self-serve
Dashboards built to the questions your team actually asks
Automations between your systems
AI workflows scoped to real tasks your team runs
Custom apps where a dashboard does not cut it
Ongoing delivery at a pace that fits your team

Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.

Before you book

Frequently asked questions.

Who owns the data?

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.

How fresh is the data?

Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.

Do I need a warehouse already?

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.

Which Crezco entities does the connector cover?

The core Payables API resources: payment requests, payments, payouts, accounts, bank-providers, mandates and customers. Each is loaded with its full state history, so you can see a payment request move from created to authenticated to paid, and tie the resulting payout back to the payments that produced it.

Does it cover both UK and EU bank-providers?

Yes. Crezco initiates payments under UK Open Banking and EU PSD2 frameworks, and the connector keeps the country and bank-provider on every payment request and payment. So a UK Faster Payments rail flow and an EU SEPA Instant flow live on the same timeline, and conversion or time-to-pay differences between them are visible per market instead of averaged together.

How do you handle refunds that arrive after the payout has cleared?

Refunds out of Crezco can land days after the original payment cleared on a payout. The connector keeps the link between the late refund, the payment it reverses and the original payout, so finance can post the reversal against the right period without re-opening a closed month-end.

GDPR-compliant

Data stays in the EU

You own the warehouse

A first deliverable live in four to six weeks.

We review your Crezco setup and the systems around it. Together we pick the first thing worth building.

Book a call See our other connectors