At a glance
The total amount that successfully flowed through Adyen in the period, gross of refunds, gross of interchange and scheme fees, gross of disputes. Money that touched Adyen’s regulated acquiring rails (web checkout + in-app + POS), not money that landed in your bank account. Adyen’s defining strength is omnichannel-on-one-platform; this card respects that and unifies online + in-store + in-app captures.
| What it counts | Every payment on the /payments Checkout API and /v68/payments Modifications endpoint where resultCode = Authorised and a subsequent capture succeeded, summed by amount.value divided by amount.currency minor-unit factor. Includes Web Drop-in, Web Components, mobile SDK, in-app, MOTO, Pay-by-Link, and unified-commerce POS captures via Adyen Terminal API. |
| API endpoint | POST /v71/payments for the authorisation; POST /v68/payments/{paymentPspReference}/captures for the capture; aggregated nightly via the Adyen Reporting API (payments_accounting_report) and webhook stream AUTHORISATION + CAPTURE. |
| VAT / tax treatment | Inclusive. The figure is whatever the customer was charged. Adyen is an acquirer-processor, not a tax engine. Tax handling sits upstream in Shopify Plus, Adobe Commerce, BigCommerce Enterprise, or the merchant’s order-management system. |
| Currency | Multi-currency native, no FX applied here. Adyen settles natively in 30+ currencies via local acquiring relationships. EUR transactions stay EUR, GBP stays GBP, USD stays USD, JPY stays JPY. Each transaction sums in its own amount.currency. For merchants who want a single FX-rolled figure, see the per-region breakdown card. |
| Fees / processing cost | Gross. Adyen Interchange++ pricing (interchange + scheme fee + Adyen markup) is NOT deducted. Net-of-fees view sits in the Adyen Customer Area Settlement report; this card shows top-line acquired volume. |
| Refunds | NOT deducted. Refunds are tracked separately as Refund modifications on the /v68/payments/{pspReference}/refunds endpoint and counted in ady_refund_volume. A fully refunded EUR 100 capture still contributes EUR 100 here. |
| Disputes / chargebacks | NOT deducted. Disputes (CHARGEBACK, NOTIFICATION_OF_CHARGEBACK, CHARGEBACK_REVERSED webhook events) are tracked separately. A successful capture later disputed still counts here. |
| Failed / declined payments | Excluded. Only successfully-captured authorisations contribute. Refused, Cancelled, Error, and Pending (where capture never succeeded) are excluded; declines are counted in ady_decline_rate. |
| 3DS 2 treatment | Both frictionless and challenge-completed flows count here. Adyen’s RevenueProtect risk engine routes most EEA traffic through 3DS 2.2 frictionless using device fingerprint + transaction risk; abandoned challenges end as Cancelled and are excluded. Track abandons in ady_threedsecure_abandon_rate. |
| Tokenization | Card-on-file rebills via Adyen tokenization (storedPaymentMethodId) and network tokens (Visa VTS / Mastercard MDES) are both Authorised + captured and contribute. Adyen’s account-updater service reduces silent expiry decline; recovered rebills count here. |
| Channels | Online + in-app + POS unified. This is Adyen’s signature feature. Web checkout, mobile-app SDK, MOTO, Pay-by-Link, and Terminal API in-store captures all flow through the same payments rail and contribute to this single number. |
| Payout timing | Per transaction date (when the customer paid), NOT per payout date (when Adyen wired your bank). Adyen settlement timing depends on the payout cycle configured (daily, weekly, manual) and currency (T+1 to T+3 typical). See ady_avg_settlement_days. |
| Time window | 30D vsP (default 30D vs the prior 30D). |
| Alert trigger | drop >15% vsP, driven by sentiment_key: revenue_trend. |
| Roles | owner, finance, operations |
Calculation
Calculated automatically from your Adyen data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A pan-European omnichannel apparel retailer (“Nordlys Apparel”), Adyen’s typical ICP, runs 28 stores across Norway, Sweden, Denmark, Germany, the Netherlands, and the UK, plus a Shopify Plus B2C site routing all card payments through Adyen, plus a native iOS app using Adyen’s iOS SDK. The 30-day window covers 03 Apr 26 to 02 May 26.| Channel | Authorisations captured | Amount | Currency | Notes |
|---|---|---|---|---|
| Web checkout (Shopify Plus + Adyen Web Drop-in) | 38,420 | EUR 4,128,000 | EUR | DACH + Benelux + Nordics, 3DS 2 frictionless 84% |
| Web checkout, UK customers | 6,810 | GBP 712,400 | GBP | Settled to GBP IBAN via local UK acquiring |
| Web checkout, Nordic customers (NOK / SEK / DKK) | 9,240 | NOK 11,840,000 | NOK | Settled NOK to a Norway IBAN, no FX |
| SEK 8,920,000 | SEK | Settled SEK | ||
| DKK 6,140,000 | DKK | Settled DKK | ||
| Native iOS app captures | 4,180 | EUR 482,000 | EUR | Apple Pay + saved card, 96% frictionless |
| Terminal API (in-store, 28 locations) | 71,400 | EUR 6,210,000 | EUR | Card-present, EMV chip + PIN |
| GBP 1,480,000 | GBP | UK stores | ||
| MOTO + Pay-by-Link (B2B account managers) | 940 | EUR 218,000 | EUR | Recurring B2B order intake |
| Refunds (period, separate) | 1,820 | EUR 92,000 | EUR | Tracked in ady_refund_volume |
| Disputes raised (period, separate) | 124 | EUR 18,400 | EUR | Tracked in ady_dispute_rate |
| Authorised but not captured | 6,210 | EUR 412,000 | - | Excluded (auth-only fashion holds, never captured) |
| Refused / declined | 4,180 | - | - | Excluded, in ady_decline_rate |
- One number across web, app, and 28 physical stores. This is the single biggest reason Nordlys chose Adyen over Stripe. On Stripe, in-store via Stripe Terminal sits in a separate reporting silo, and the iOS in-app SDK sits in a third silo; rolling them up requires custom BI work. Adyen’s unified-commerce platform delivers EUR 11.04m as one figure with channel-tagged drilldown.
- Five currencies natively settled, no FX margin paid. Nordlys has six legal entities (one per country) and Adyen settles each currency to the matching local IBAN without FX conversion. On Stripe the same setup would either force a single home-currency settlement (Stripe charging 1% FX spread on the four foreign currencies) or require Stripe Treasury balances per currency. Adyen’s local-acquiring footprint is the structural feature here.
- 84% 3DS 2.2 frictionless on EEA web traffic. Adyen’s RevenueProtect feeds device-fingerprint + behavioural-risk data into the 3DS 2.2 challenge decision; healthy integrations on EEA cards typically achieve 80, 90% frictionless. Below 75%, your
merchantRiskIndicatorpayload is weak; above 92% suggests issuer trusted-merchant status. - MOTO + Pay-by-Link for B2B sits in the same total. Adyen treats Pay-by-Link captures as the same
Authorised + capturedrail; this is unusual, on most PSPs Pay-by-Link is a separate product with separate reporting. Useful for merchants who use it for B2B account-manager-driven intake. - Authorised-but-not-captured sits outside this card. EUR 412k of authorisations that Nordlys placed (likely fashion try-before-you-buy holds) but never captured are excluded. Stripe and Braintree treat this differently in their dashboards, on Adyen, only captures count toward acquired volume. This is the conservative, audit-correct treatment.
Sibling cards merchants should reference together
| Card | Why merchants reach for it next to Total Volume |
|---|---|
ady_total_transactions | Transaction count over the same window. Volume divided by count = average transaction. |
ady_avg_transaction | The denominator-aware reading; useful for spotting basket-mix changes. |
ady_volume_trend | This metric trended daily over the window, the first card to open when the headline moves. |
ady_top_payment_methods | Per-method breakdown (iDEAL, SEPA, Klarna, Apple Pay, card schemes). Critical on Adyen because local methods are a large share of EU volume. |
ady_refund_volume | The amount to subtract for a net-of-refunds figure. |
ady_payouts_pending | What is in flight from this volume but not yet settled to your bank. |
Stripe stripe_total_revenue / PayPal pp_total_volume | Same archetype on competing rails. Multi-PSP merchants sum these for total payment volume. |
Shopify total_revenue / BC total_revenue / Adobe total_revenue | Upstream commerce view. Adyen volume should reconcile to (commerce_total minus non-Adyen-method orders). |
Reconciling against the vendor’s own dashboard
Where to look in the Adyen Customer Area: Sign in to the Adyen Customer Area at ca-live.adyen.com (orca-test.adyen.com for test). The closest comparable view is:
Transactions → Payments (filter by date range; “Result: Authorised” + capture confirmed)The headline tile on the Transactions overview also shows period acquired volume. For the omnichannel breakdown, use Reports → Standard reports → Payments accounting report which separates by
Source (web, mobile_sdk, terminal, moto, payment_link).
Other Adyen Customer Area views that look similar but answer different questions:
- Settlement details report (Reports → Settlement details). This is post-fee, post-reserve, FX-converted settled balance, NOT gross transaction volume. Always lower than this card. Use
ady_payouts_pendingand Adyen’s blended fee rate to bridge. - Disputes overview (Risk → Disputes). Tracks chargeback / RFI cases, not transaction volume.
- In-Person Payments (Point of sale → Transactions). Per-terminal end-of-day reports. These are a subset of this card (POS-only, one terminal or store).
- MarketPay / Adyen for Platforms balance (where enabled). For platform merchants splitting payments to sub-merchants, this view shows the platform’s residual after splits, not gross marketplace volume.
| Reason | Direction | Why |
|---|---|---|
| Time zone | Boundary days off | Adyen Customer Area renders in your account’s configured timezone (Amsterdam by default for EU merchants, configurable per user). Vortex IQ uses UTC for period boundaries. For a 30-day window the gap averages out; for “today” or “yesterday” cards it can shift the figure meaningfully. |
| Capture window | Theirs may show authorisation, ours captures only | Adyen Customer Area can be filtered to “Authorised” (auth-only) or “SettledExternally” (captured + settled). This card uses captures, the audit-correct money-actually-taken view. Auth-only volumes are typically 5, 15% higher because of un-captured fashion holds. |
| FX conversion | Theirs may be EUR-equivalent, ours native | Adyen Customer Area offers a “Convert to display currency” toggle that uses Adyen’s FX rate. This card preserves native currency. For an FX-rolled view see the per-region card. |
| Reserve holds | Theirs lower (Settlement details view) | Adyen can hold a small reserve for newly-onboarded merchants or seasonal businesses; the Settlement details view nets this off. This card is gross of reserves. |
| Refresh lag | Ours lower for “today” | Our index updates on a periodic sync of the Adyen Reporting API plus webhook stream; the most recent 5, 15 minutes of captures may not be reflected. Yesterday and earlier are caught up. |
| Cancelled-after-capture edge case | Ours updates on next sync | A capture that the merchant or Adyen reverses (CANCEL_OR_REFUND modification in the same day) flips state in Adyen; we update on the next webhook flush. Gap closes within minutes. |
| Comparison | Expected relationship | When divergence is legitimate |
|---|---|---|
ady_total_volume ↔ shopify.total_revenue | adyen ≤ shopify | Shopify totals include orders paid via Shop Pay, Apple Pay direct, PayPal, Klarna direct, gift cards, manual bank transfer, none of which touch Adyen unless routed through Adyen. For a Shopify-Plus + Adyen Enterprise setup, expect Adyen to cover 80, 95% of card-method revenue. |
ady_total_volume ↔ adobe_commerce.total_revenue | adyen ≤ adobe_commerce | Same logic. Adobe Commerce supports many gateways; each one displaces Adyen revenue. Adyen is a common Adobe Commerce enterprise gateway. |
ady_total_volume ↔ bigcommerce.total_revenue | adyen ≤ bigcommerce | Same logic. |
ady_total_volume + stripe.stripe_total_revenue + paypal.pp_total_volume | ≈ commerce_total_revenue (in matching currency) | The three payment-processor volumes summed should approach the commerce platform total. They should never exceed it. If they do, there is likely double-counting (a marketplace split routed through both rails) or a refund/chargeback timing mismatch. |
Known limitations / merchant FAQs
Reconciliation questions (“why doesn’t this match the Adyen Customer Area / my bank?”) are answered in the Reconciling against the vendor’s own dashboard section above. Below are the questions that aren’t reconciliation.“Why is Adyen typically more expensive than Stripe at SMB volumes but cheaper at enterprise volumes?” Pricing model. Stripe’s standard SMB tariff is a flat blended rate (1.4% + 0.20 EUR for EEA cards on Standard pricing); Adyen runs Interchange++ by default, which exposes interchange + scheme fee + Adyen markup separately. At small merchant volume, Stripe’s flat rate is competitive and operationally simpler; at enterprise volume (typically 50m+ EUR/year), Adyen’s Interchange++ recovers the interchange spread that Stripe pockets, often saving 20, 40 basis points blended. The structural break-even depends on your card mix (heavy AmEx and corporate-card mix favours Adyen sooner; heavy domestic-debit favours Adyen even sooner). Multi-currency and local acquiring are usually the deciding factor regardless of price. “Adyen for Platforms vs Stripe Connect for marketplaces, what changes for this number?” Adyen for Platforms (formerly MarketPay) splits payments to sub-merchants under the regulated payment institution umbrella; the platform is the merchant of record by default but the legal arrangement is configurable. This card shows acquired volume for your platform account; sub-merchant residuals are visible separately. Stripe Connect’s Standard accounts make each sub-merchant the merchant of record, so the platform’s
total_volume is just platform-fee revenue; Adyen’s model gives the platform full visibility on gross. Choose accordingly when reading this number for marketplace operators.
“Does Adyen settle natively in multiple currencies, or convert everything to EUR?”
Native in 30+ currencies. Adyen has local acquiring relationships in EU (EUR settled to local IBANs per country), UK (GBP), US (USD), Japan (JPY), Australia (AUD), Singapore (SGD), Hong Kong (HKD), Brazil (BRL), Mexico (MXN), and others. A Dutch-headquartered merchant accepting GBP from UK customers can settle directly to a UK GBP bank account without FX, materially cheaper than the Stripe model where everything either converts to your home currency at Stripe FX (1% spread) or requires Stripe Treasury balances per currency. This card respects native settlement, you’ll see EUR + GBP + NOK + SEK + DKK listed alongside each other, not converted.
“3DS 2.2 frictionless rate, what is healthy on Adyen?”
80, 90% frictionless on EEA card-not-present traffic is the live benchmark for healthy Adyen Web Drop-in / Web Components integrations. Adyen’s RevenueProtect engine is one of the strongest 3DS 2.2 frictionless drivers in the market because it ingests device fingerprint + behavioural risk + transaction-context data into the issuer-facing merchantRiskIndicator payload. Below 75% frictionless, your threeDS2RequestData is incomplete (typically missing browser data, missing acctInfo for stored cards, or weak device fingerprint). Track this and 3DS abandonment in ady_threedsecure_abandon_rate.
“Why does this number include Terminal API captures? My CFO wants online-only.”
Adyen’s defining product feature is unified-commerce reporting, web + in-app + Terminal API all flow through the same /payments rail and contribute as Authorised + captured. To filter to online only, drill down by Source (web, mobile_sdk, terminal, pos, moto, payment_link). The Adyen Customer Area’s Reports → Standard reports → Payments accounting report has the canonical breakdown.
“Authorised but not captured, why is that excluded?”
Adyen separates authorisation (the issuer holds funds) from capture (the funds actually move to your acquiring account). For fashion try-before-you-buy holds, hotel pre-auths, marketplace escrow, and B2B order verification, many authorisations never become captures. This card uses captures only because that’s the audit-correct money-actually-taken view; it matches what you settle. Auth-only volume sits in a separate operational metric.
“Adyen account updater, what does it do for my recurring rebill volume?”
Adyen subscribes to Visa’s Account Updater Service (AUS) and Mastercard’s Automatic Billing Updater (ABU). When a stored card expires or is reissued, the new pan/expiry is silently swapped into your storedPaymentMethodId token without merchant action. This recovers 8, 25% of would-be-failed rebills depending on portfolio age and BIN mix. Recovered rebills count in this card; failed-rebills-not-recovered are excluded.
“RevenueProtect (Adyen’s risk engine) vs Stripe Radar, how do I read this card differently?”
Both are post-authorisation fraud filters, both can suppress acquired volume. Adyen’s RevenueProtect runs by default for all Adyen merchants and can be configured by rule + ML score; Stripe Radar runs by default with a single ML score. If you tighten RevenueProtect rules, you’ll see this card drop and ady_decline_rate rise correspondingly; if you loosen, the inverse. The decision is a fraud-vs-revenue trade off; aim for an ady_chargeback_rate below 0.5% and a decline rate that doesn’t punish good cards.
“Why is the customer-paid total higher than what arrived in my Adyen settlement bank account?”
Three deductions between this card and your IBAN: (1) Adyen Interchange++ (typically 1.0, 1.8% blended for EEA cards depending on card mix; higher for AmEx and non-EEA), (2) refunds processed in the same window, (3) settlement timing (transactions on the last day of the period may settle the next cycle). Use the Settlement details report in the Adyen Customer Area together with this card to bridge. The gap is also affected by FX if your settlement currency differs from acquiring currency (avoid by configuring local-currency IBANs).