Razorpay for WooCommerce writes razorpay_payment_id, razorpay_signature, refund IDs, and is_magic_checkout_order to order meta on every Razorpay-paid order. Storage adapts to HPOS (wc_orders_meta) or legacy (postmeta). The default WooCommerce reports do not split by gateway, which leaves Razorpay-only revenue and Magic Checkout cohort analysis invisible to growth and finance.

SleekView Charts pivots the razorpay_* keys and builds a gateway-scoped dashboard. A KPI card shows Razorpay revenue for the period. An Area card plots daily revenue against the Razorpay subset. A Pie card splits orders by status (completed, processing, refunded, failed). A Bar card compares orders with and without the Magic Checkout flag, which is the core conversion experiment for Indian D2C stores.

Mode and gateway filters keep the dashboard scoped to Razorpay-paid orders. Drill-through into the matching rows surfaces the payment ID and signature for fast reconciliation against the Razorpay dashboard.

Razorpay's WooCommerce plugin writes the right metadata for gateway-aware reporting, but the WooCommerce reports screen treats all orders the same and the per-order meta panel hides the data behind clicks. For Indian D2C stores running Razorpay plus COD plus another gateway, the question of how Razorpay specifically is performing simply does not get answered without exports. A gateway-scoped dashboard built directly on the razorpay_* meta closes that gap.

Revenue and daily trend scoped to Razorpay-paid orders gives finance a clean settlement view. Status mix surfaces refund waves and failed-payment patterns. The Magic Checkout vs standard bar is the only place outside a paid analytics warehouse where the alternative checkout flow's revenue lift gets a real chart.

Drill-through into rows preserves the payment ID column, so cross-reference against Razorpay's own dashboard is a click rather than a copy-paste between tabs. The gateway still owns refunds and the canonical settlement; the dashboard owns the WordPress-side visibility that the meta-key persistence pattern always implied.