How to build Adyen payment dashboards in Metabase

Adyen is an enterprise payments platform processing online, in-app, and in-person payments worldwide, with detailed settlement and fee data. Metabase is where you turn that into shared dashboards for authorization rate, net settlement, chargebacks, and fees. Because Metabase reads from SQL databases, the reliable way to connect them is a small pipeline: sync Adyen into a database or warehouse on a schedule, then point Metabase at it. This guide walks through that path end to end — including a free option with no paid connector.

How do you connect Adyen to Metabase?

Metabase connects to SQL databases and warehouses — not to SaaS APIs directly, and there's no native Adyen connector. So connecting Adyen to Metabase means one thing: run a small pipeline that copies Adyen data into a database on a schedule, then connect Metabase to that database. Once the data lands, the models, metrics, and SQL later in this guide all work.

The good news: this doesn't require a paid tool. Use a managed connector if you want zero maintenance, or a free, code-based sync you host yourself — both are covered in Build the pipeline below, and in more depth in our guide to building a data pipeline.

What can you analyze from Adyen data in Metabase?

• Authorization rate — authorised ÷ attempted, by method, issuer, and country
• Processed and net volume — captured volume and what settles after fees
• Fees — interchange, scheme, and Adyen markup as a share of volume
• Refunds and chargebacks — leakage and risk vs. scheme thresholds
• Settlement — timing and net amounts by currency
• Payment methods — mix and performance across channels

Which Adyen dashboards should you build in Metabase?

How do you build the Adyen → Metabase pipeline?

For dashboards that need history and reliability, land Adyen data in a database first, then connect Metabase to that database.

Connector options

• Settlement detail reports (free, first-party) — the definitive record of captures, fees, and net settlement; load them on a schedule.
• Adyen APIs (free, raw) — Checkout, Management, and reporting APIs for payment and dispute detail.
• Webhooks (free, events) — stream authorisation, capture, refund, and chargeback notifications into a table.

Notes

• Land raw reports first, then build clean models on top.
• Settlement detail reports are the source of truth for net revenue — model fees (interchange, scheme, markup) from them.
• Adyen is multi-currency — convert to one reporting currency or split by it.
• Amounts are in minor units — divide in a model layer.

Can you generate an Adyen dashboard with AI?

Yes — and once Adyen data is synced into a database, this is the fastest way to a strong first draft. First give an AI assistant a way to read your Metabase schema and create questions and dashboards, then paste the prompt below. It builds the dashboard from your database tables and tells the agent to skip metrics the schema can't support instead of faking them.

Two ways to let an assistant query and build in Metabase

Both connect to a Metabase instance that's already pointed at your synced database — the pipeline above moves the data; these just let the assistant read and write Metabase. Pick whichever fits your setup:

Set up the Metabase MCP server

Enable it under Admin → AI → MCP, then point your client at the endpoint:

# Metabase built-in MCP (replace with your instance URL)
claude mcp add --transport http metabase https://your-metabase.example.com/api/metabase-mcp

{
  "mcpServers": {
    "metabase": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://your-metabase.example.com/api/metabase-mcp"]
    }
  }
}

Clients with native remote support can use a "url" field instead of the mcp-remote bridge. Confirm the current endpoint in the Metabase MCP docs.

Set up the Metabase CLI

Install it globally, then authenticate once (the binary is mb):

# Install the CLI (the binary is `mb`)
npm install -g @metabase/cli

# Authenticate once — opens your browser on Metabase v62+, or use an API key
mb auth login --url https://your-metabase.example.com
mb auth status

On Metabase v62+ mb auth login opens your browser; older servers fall back to an API key. A terminal-based assistant can then inspect your schema (mb db schemas, mb table get --include fields) and create content (mb card create, mb dashboard create) against the synced tables.

Prompt: build the Adyen Payments Overview dashboard

With MCP or the CLI connected, paste this into your assistant to generate the dashboard:

Create a polished Metabase dashboard for Adyen payments analytics using the
available Adyen tables in this database.

Goal: Help payments and finance leaders understand authorization rate, processed
and net volume, refunds, chargebacks, fees, and settlement from Adyen data.

First, inspect the schema and identify the available Adyen tables (often from
settlement detail reports plus API data). Do not assume exact table names. Map
the raw data into these analytical concepts where possible: Payments
(authorisations), Captures, Refunds, Chargebacks/Disputes, Fees (interchange,
scheme, markup), Settlements, and Payouts.

Important:
- Build the dashboard from durable database/warehouse tables (settlement detail
  reports and the APIs).
- Compute authorization rate as authorised ÷ attempted, and segment by method,
  issuer, and country.
- Separate processed volume from net settlement (after interchange, scheme, and
  Adyen fees).
- Track chargeback rate against scheme thresholds.
- Report in a single reporting currency; Adyen is multi-currency, so convert
  with a documented rate or split by currency.
- Do not claim Metabase connects natively to Adyen unless that is explicitly
  true in this environment.

Dashboard title: Adyen Payments Overview

Sections:
1. Executive summary (KPI cards): Processed volume; Net settlement; Authorization
   rate; Refund rate; Chargeback rate; Fees %.
2. Authorization & conversion: Auth rate by day; by method/issuer; declines by
   reason.
3. Volume & net settlement: Processed vs. captured; Net settled; Fee breakdown.
4. Refunds & chargebacks: Refund rate; Chargebacks vs. thresholds; Win/loss rate.
5. Settlement & fees: Settlement timing; Fees as a share of volume; Net
   settlement by currency.

Filters: Payment method, Issuer, Country, Currency, Date range.

Before finalizing, create or recommend reusable Metabase models:
modeled_adyen_payments, modeled_adyen_settlement_details, and
modeled_adyen_chargebacks.

Output: Build the dashboard if you have permission; otherwise provide the exact
questions, SQL, model definitions, and layout. Include caveats for any metric
that cannot be calculated from the available schema. Reconcile totals against
Adyen Customer Area. Keep it practical, dense, and executive-readable. Avoid
vanity metrics.

How should you model Adyen data in Metabase?

Core tables

Modeling advice

• Treat settlement_details as the source of truth for net revenue and fees.
• Build a modeled_adyen_payments view keyed on psp_reference to link authorisation, capture, refund, and chargeback.
• Define authorization rate on a consistent attempt denominator.
• Break fees into interchange, scheme, and markup so cost is transparent.
• Reconcile modeled net settlement against the Adyen Customer Area.

Which Adyen metrics should you track in Metabase?

What SQL powers Adyen dashboards in Metabase?

These assume the modeled tables above (PostgreSQL dialect, amounts in minor units). Adjust identifiers to match your schema.

SELECT
  date_trunc('day', created_at)                       AS day,
  COUNT(*)                                            AS attempts,
  COUNT(*) FILTER (WHERE result = 'Authorised')       AS authorised,
  ROUND(100.0 * COUNT(*) FILTER (WHERE result = 'Authorised')
    / NULLIF(COUNT(*), 0), 2)                         AS auth_rate_pct
FROM payments
WHERE created_at >= CURRENT_DATE - INTERVAL '30 days'
GROUP BY 1
ORDER BY 1;

SELECT
  payment_method,
  COUNT(*)                                            AS attempts,
  ROUND(100.0 * COUNT(*) FILTER (WHERE result = 'Authorised')
    / NULLIF(COUNT(*), 0), 2)                         AS auth_rate_pct
FROM payments
WHERE created_at >= CURRENT_DATE - INTERVAL '30 days'
GROUP BY payment_method
ORDER BY attempts DESC;

-- Net settlement from settlement detail records
SELECT
  date_trunc('month', booking_date)                   AS month,
  ROUND(SUM(gross_debit - gross_credit) / 100.0, 2)   AS gross_amount,
  ROUND(SUM(commission + markup + scheme_fees + interchange) / 100.0, 2)
    AS total_fees,
  ROUND(SUM(net_debit - net_credit) / 100.0, 2)       AS net_settled
FROM settlement_details
GROUP BY 1
ORDER BY 1;

What are common mistakes when analyzing Adyen in Metabase?

Related

Related analytics

Related metrics

Related integrations

FAQ