At a glance
The aggregate gross authorised + captured value moving across Viva Payments rails in the period: online Smart Checkout, Smart POS card-present, Recurring Payments rebills, Marketplace Splits gross, and pay-by-link. The “how much money touched the rail” view, before refunds, fees, FX, or settlement timing.
Calculation
Calculated automatically from your Viva Payments 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 French DTC subscription-coffee retailer (“Café Lumière”) operates a Shopify storefront with Viva Smart Checkout as the primary EU processor, plus one Smart POS at their Lyon roastery counter. They also use Viva Recurring Payments for monthly subscription rebills. The 30-day window covers 03 Apr 26 to 02 May 26.- Recurring is 14.7% of EUR volume. Subscription rebills (EUR 58,200) are silently the second-largest channel. A 1pp drop in subscription retention costs roughly EUR 580/month at this volume; this is why subscription-led merchants treat Viva Recurring as a first-class metric.
- Pay-by-link is small but high-AOV. 28 captures generating EUR 18,400 implies an average ticket of EUR 657, materially higher than the EUR 65 e-shop average. Pay-by-link revenue per transaction is structurally higher because it’s used for B2B invoicing where amounts are larger and friction is lower.
- GBP listed alongside EUR rather than converted. A finance team looking for “single rolled-up EUR” won’t find it here; that view lives in
viva_revenue_by_country. The omission is intentional, FX-converted volume distorts treasury planning where settlement actually occurs in the native currency. - POS is the structural floor. The Lyon counter (EUR 12,400) is 3.1% of EUR volume but the Lyon team uses it for daily cash flow planning. Treating volume as a single number masks the operating reality that POS settles same-day-end while online settles within minutes via Viva-IBAN.
- 3DS 2 frictionless rate at 81% is healthy. PSD2 SCA forces 3DS challenges on EEA card-not-present payments above EUR 30. Viva’s Smart Checkout achieves frictionless on 75 to 85% of healthy traffic by feeding strong device + transaction risk data to issuers. The 19% who got challenges and the 142 abandons live in
viv_threedsecure_abandon_rate.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in the Viva Payments Dashboard: Sign in at viva.com/business/account/login. Closest comparable views:Viva Business → Sales → Transactions (filter by date range; “Status: Successful”)
Viva Business → Sales → Reports → Channels (per-channel split: online / Smart POS / recurring / pay-by-link)The headline tile on the Sales overview also shows period revenue. Other Viva views to be aware of:
- Settlements view (Sales → Settlements). Post-reserve, post-fee balance. Always lower than this card. Use
viva_net_revenueand the effective fee rate to bridge. - Disputes view (Sales → Disputes). Tracks chargeback cases, not transaction volume.
- Marketplace Splits view (Business → Marketplace, where enabled). For platform merchants, shows post-split residual; this card shows gross volume before splits.
- Smart POS terminal reports (Devices → Terminals). Per-terminal end-of-day reports. Subset of this card.
Cross-connector reconciliation, what should match what:
Quick rule for support tickets: if a merchant says “Viva Dashboard shows EUR 100k, your number shows EUR 80k” in the same period, walk through time-zone first (most common cause for Greek/Cyprus/Athens accounts), reserve-netting second (newly-onboarded merchants comparing against Settlements view), multi-currency third.
Known limitations / merchant FAQs
Reconciliation questions (“why doesn’t this match the Viva Dashboard or my bank?”) are answered in the Reconciling against the vendor’s own dashboard section above. Below are the questions that aren’t reconciliation.“Total Volume vs Total Revenue, what’s the difference?” Arithmetically the same when both are scoped to
StatusId = F. The labels reflect different audiences. Total Revenue is finance-team language (the merchant top line); Total Volume is treasury and ops language (the volume of money flowing across the rail before it becomes the merchant’s). Same number, two lenses. Some agencies prefer to see both in their dashboards, hence both cards.
“Viva is owned by JP Morgan now. Does anything change for me operationally?”
No, not at the API or merchant-account level. JP Morgan Chase acquired 49% of Viva.com in 2023 with an option to ramp to majority. Day-to-day operations (Viva Business Dashboard, Smart Checkout API, Smart POS terminals, settlement rails, fee structures, e-money licences) all continue under Viva’s existing entities. From a CFO perspective the practical implication is balance-sheet credibility (a globally systemic bank backs the platform), not workflow change. Volume figures are unaffected.
“Why is Viva often cheaper than Stripe for my Greek or Mediterranean store?”
Three reasons. (1) The Interchange Fee Regulation caps EU intra-EEA debit interchange at 0.2% and credit at 0.3%; Viva passes more of this saving through to SMBs in Greece, Cyprus, Spain, Italy, Portugal, Romania than Stripe does. (2) Viva has direct connections to Greek and Cyprus issuing banks; Stripe usually routes Greek issuers via a non-Greek acquirer, which adds basis points. (3) Greek-language support and on-the-ground POS hardware are structurally cheaper for the merchant to operate.
“Does Viva settle natively in multiple currencies?”
Yes, in 13+ currencies depending on merchant account jurisdiction and the IBAN currency you’ve configured. A Greek-headquartered merchant accepting GBP from UK customers can settle directly to a GBP IBAN without FX, materially cheaper than Stripe’s model where everything either converts to home currency at Stripe FX (1% spread) or sits in a Stripe Treasury balance. This card respects native settlement.
“Why does this number include POS captures? My CFO wants online-only.”
Viva’s defining product feature is omnichannel unified reporting, POS and online both flow through the same Payments API as Type = Capture. To filter to online only, use the SourceCode field. The Viva Dashboard’s Sales → Reports → Channels view already provides the split. A per-channel split card is on the roadmap.
“3DS 2 frictionless rate, what’s a healthy number?”
75 to 85% frictionless on EEA card-not-present traffic is the live benchmark for healthy Smart Checkout integrations. Below 70%, your device fingerprint or risk data feed to issuers is weak (often a misconfigured MerchantTrxId or missing browser data). Above 90% suggests you’re in issuer trusted-merchant allowlists, which is excellent. Track via viv_threedsecure_abandon_rate.
“My recurring subscription rebills, do those count here?”
Yes. Viva Recurring Payments uses tokenized card-on-file (network-token-backed where the issuer supports VTS / MDES) and rebills as Type = Capture against the original token. They’re indistinguishable from one-time captures in this card. Track them separately via the RecurringTransactionId field; a dedicated Subscription Volume card is on the roadmap.
“What’s the difference between Viva volume and Viva net deposited?”
Three deductions between this card and your IBAN: (1) Viva’s blended fee (typically 0.8 to 1.4% for EU cards), (2) refunds processed in the same window, (3) settlement timing (transactions on the last day of the period may settle the next day for non-Viva-IBAN accounts). Use Net Revenue and the Settlements view together to bridge.
“What about Viva’s API rate limits?”
Production tier: typically 10 requests/sec, 600/min, with bursts permitted. For merchants doing more than 50,000 transactions/day, the engine batches reads to stay under cap; the practical effect is a 5 to 15-minute lag on the freshest transactions. If you’re consistently above the rate limit, contact Viva merchant support for a tier upgrade.