Support Spike on Refused Payments, Adyen

Support Spike on Refused Payments for Adyen. Tracked in the Vortex IQ Nerve Centre, how to read it, why it matters, and how to act on it.

Metrics type: Key Metrics • Category: Cross-Platform: Payments to Revenue

Support Spike on Refused Payments as reported by the Adyen integration.

At a glance

Support Spike on Refused Payments is a cross-platform: 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-platform card: it joins Adyen to a sibling connector to surface insight neither shows alone. Gated: renders only when sibling support_helpdesk connector (intercom) connected.

What it counts	Support Spike on Refused Payments 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-Platform: 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	number
Time window	7D
Alert trigger	>0 refused-payment shoppers in support
Sentiment key	-
Roles	owner, finance, operations

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 Support Spike on Refused Payments 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_revenue_reconciliation	Cross-Platform: Payments to Revenue sibling: Captured vs Commerce Revenue.
ad_xc_refund_vs_commerce	Cross-Platform: 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.