> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Captured vs Commerce Revenue, Adyen

> Captured vs Commerce Revenue for Adyen. Tracked in the Vortex IQ Nerve Centre — how to read it, why it matters, and how to act on it.

**Card class:** [🦸 Hero](/nerve-centre/overview#card-classes-explained)  •  **Category:** [Cross-Channel: Payments to Revenue](/nerve-centre/connectors#connectors-by-type)

> Captured vs Commerce Revenue as reported by the Adyen integration.

## At a glance

> **Captured vs Commerce Revenue** is a cross-channel: payments to revenue metric tracked from Adyen data. It surfaces operational signal so you can spot regressions, opportunities, and structural patterns. Cross-reference the sibling cards below for the full diagnostic picture. This is a cross-channel card: it joins Adyen to a sibling connector to surface insight neither shows alone. Gated: renders when — sibling ecommerce\_platform / marketplace connector connected.

|                       |                                                                                                                                                                                          |
| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**    | Captured vs Commerce Revenue as reported by the Adyen integration.                                                                                                                       |
| **Sample type**       | Backend API data from Adyen, refreshed on the standard data refresh.                                                                                                                     |
| **Why it matters**    | The metric appears in the Cross-Channel: Payments to Revenue category and complements the sibling cards listed below. Track movement over time to identify regressions or opportunities. |
| **Reading the value** | Compare the current period to the prior period to read direction. Cross-reference siblings to triangulate cause.                                                                         |
| **Format**            | currency                                                                                                                                                                                 |
| **Time window**       | `30D`                                                                                                                                                                                    |
| **Alert trigger**     | `>2% mismatch`                                                                                                                                                                           |
| **Sentiment key**     | —                                                                                                                                                                                        |
| **Roles**             | owner, finance                                                                                                                                                                           |

## Calculation

Calculated automatically from your Adyen data on the standard refresh. See the At a glance summary for what it tracks and the worked example below for a typical reading.

## Worked example

*A representative reading of **Captured vs Commerce Revenue** for a typical Adyen account.* The card reports the current value alongside a comparison against the previous period — direction matters. When it moves outside the expected range, cross-reference the siblings below to find the cause; use Vortex Mind to trace upstream causes and Ask Viq for natural-language exploration.

## Sibling cards merchants should reference together

| Card                                                                                              | Why merchants reach for it                                                     |
| ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| [`ad_xc_failed_payment_support`](/nerve-centre/kpi-cards/adyen/support-spike-on-refused-payments) | Cross-Channel: Payments to Revenue sibling: Support Spike on Refused Payments. |
| [`ad_xc_refund_vs_commerce`](/nerve-centre/kpi-cards/adyen/refunds-vs-commerce-returns)           | Cross-Channel: Payments to Revenue sibling: Refunds vs Commerce Returns.       |

## Reconciling against the vendor's own dashboard

**Where to look in Adyen's own dashboard:** find this metric (or its components) under the relevant report/section. Confirm the period boundaries and any filters match the Vortex IQ profile to reconcile cleanly. The Vortex IQ value may legitimately differ due to period definition, time zone, sampling, or how the vendor buckets the underlying records.