How to build Razorpay payment dashboards in Metabase

# Razorpay (local NPX server)
claude mcp add razorpay \
  --env RAZORPAY_KEY_ID=<YOUR_KEY_ID> \
  --env RAZORPAY_KEY_SECRET=<YOUR_KEY_SECRET> \
  -- npx -y @razorpay/mcp-server@latest

{
  "mcpServers": {
    "razorpay": {
      "command": "npx",
      "args": ["-y", "@razorpay/mcp-server@latest"],
      "env": {
        "RAZORPAY_KEY_ID": "<YOUR_KEY_ID>",
        "RAZORPAY_KEY_SECRET": "<YOUR_KEY_SECRET>"
      }
    }
  }
}

# Install the Metabase CLI
npm install -g @metabase/cli

# Log in (opens your browser; requires Metabase v62+)
mb auth login --url https://your-metabase.example.com

# Load a Razorpay CSV export — creates a table AND a model
mb upload csv --file razorpay-payments.csv --collection root

# Refresh that same table later from a new export
mb upload replace <table-id> --file razorpay-payments.csv

Create a polished Metabase dashboard for Razorpay payments analytics.
Work end to end: get the data into Metabase if it isn't there yet, then build.

Goal: Help founders and finance leaders understand captured volume, net revenue,
payment success, refunds, disputes, settlements, and (if used) subscriptions/MRR
from Razorpay data.

Step 1 — Find or load the data:
- First, check what already exists in Metabase (search for Razorpay tables and
  models). If durable Razorpay data is already present — synced from a warehouse
  or uploaded earlier — use it and skip to Step 2.
- If nothing is there, pull it with the Razorpay MCP server using read-only API
  keys: payments, orders, settlements, refunds, disputes, and subscriptions.
  Write each result to a CSV, then load it with the Metabase CLI — run
  "mb upload csv --file <export>.csv" so each upload creates a table and a
  ready-to-query model. Use "mb upload replace <table-id> --file <export>.csv" to
  refresh an existing table instead of creating duplicates.

Step 2 — Inspect before querying:
Do not assume exact table names. Map the available raw tables into these
analytical concepts where possible: Payments, Orders, Settlements, Refunds,
Disputes, Customers, and Subscriptions. Inspect the actual tables and column
names first.

Important:
- Build on whatever data is present; don't claim Metabase connects natively to
  Razorpay — it reads a database or CLI-uploaded tables.
- Separate gross captured volume from net revenue (after Razorpay fees and tax).
- Compute payment success rate as captured ÷ attempted, and segment by method
  (UPI, cards, netbanking, wallets).
- If Razorpay Subscriptions are used, compute MRR from active subscriptions.
- Report in INR (or your settlement currency); note the currency.
- Only build a card if its underlying column/metric exists in the data.
- A single CSV is a point-in-time snapshot: volume and success-rate trends need
  history, so build trend cards only if a warehouse sync or multiple uploads
  provide it.

Dashboard title: Razorpay Payments Overview

Sections:
1. Executive summary (KPI cards): Captured volume; Net revenue; Success rate;
   Refund rate; Dispute rate; Average transaction value.
2. Volume & net revenue: Volume by day; Gross vs. net; Average transaction
   value.
3. Success & failures: Success rate; Failures by reason; Success by method.
4. Refunds, disputes & settlements: Refund rate; Disputes by month; Settlement
   timing; Fees as a share of volume.
5. Subscriptions & MRR (if used): MRR movement; Active subscriptions; Revenue
   churn.

Filters: Method, Currency, Order/product, Date range.

Reuse the models Metabase auto-created from uploaded CSVs, or (for a warehouse)
create reusable models: modeled_razorpay_payments, modeled_razorpay_settlements,
and (if used) modeled_razorpay_mrr.

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 data. Reconcile totals against
Razorpay Dashboard. Keep it practical, dense, and executive-readable. Avoid
vanity metrics.

Captured volume and how reliably payments go through.

SELECT
  date_trunc('day', to_timestamp(created_at))         AS day,
  COUNT(*)                                            AS payments,
  COUNT(*) FILTER (WHERE status = 'captured')         AS captured,
  ROUND(100.0 * COUNT(*) FILTER (WHERE status = 'captured')
    / NULLIF(COUNT(*), 0), 2)                         AS success_rate_pct,
  ROUND(SUM(amount) FILTER (WHERE status = 'captured') / 100.0, 2)
    AS captured_volume
FROM payments
WHERE to_timestamp(created_at) >= CURRENT_DATE - INTERVAL '30 days'
GROUP BY 1
ORDER BY 1;

Compare UPI, cards, netbanking, and wallets.

SELECT
  method,
  COUNT(*)                                            AS attempts,
  ROUND(100.0 * COUNT(*) FILTER (WHERE status = 'captured')
    / NULLIF(COUNT(*), 0), 2)                         AS success_rate_pct
FROM payments
WHERE to_timestamp(created_at) >= CURRENT_DATE - INTERVAL '30 days'
GROUP BY method
ORDER BY attempts DESC;

Net revenue is what lands after Razorpay fees.

SELECT
  date_trunc('month', to_timestamp(created_at))       AS month,
  ROUND(SUM(amount) / 100.0, 2)                       AS gross_volume,
  ROUND(SUM(fee) / 100.0, 2)                          AS fees,
  ROUND(SUM(amount - fee) / 100.0, 2)                 AS net_revenue
FROM payments
WHERE status = 'captured'
GROUP BY 1
ORDER BY 1;