At a glance
The total amount that successfully flowed through Viva Payments in the period, gross of refunds, gross of interchange and scheme fees, gross of disputes. Money that touched Viva’s regulated payment institution rails (online checkout + Smart POS + recurring), not money that landed in your bank account.
| What it counts | Every transaction on /api/transactions (Smart Checkout) and POS captures where StatusId = F (Successful), summed by Amount, in each transaction’s CurrencyCode. Includes online checkout, Smart POS card-present, and recurring rebills. |
| API endpoint | GET /api/transactions on the Smart Checkout API; cross-referenced with /payments for source-of-truth state. OAuth 2.0 client-credentials at accounts.vivapayments.com/connect/token. |
| VAT / tax treatment | Inclusive. The figure is whatever the customer was charged at terminal or online. Viva is a payment institution, not a tax engine, tax handling sits upstream in the commerce platform (Shopify / BigCommerce / Adobe / Magento). |
| Currency | Multi-currency native settlement, no FX applied here. Viva natively settles in EUR, GBP, RON, CHF, USD, BGN, HRK, HUF, PLN, CZK, DKK, NOK, SEK, depending on merchant account jurisdiction. Each transaction is summed in its own CurrencyCode; pan-EU merchants will see EUR + GBP + RON arithmetically. Use Revenue by Country for the unambiguous breakdown. |
| Fees / processing cost | Gross. Viva interchange + scheme + acquiring fees (typically 0.8, 1.4% for EU intra-EEA debit cards under PSD2 IFR cap, higher for AmEx and non-EEA cards) are NOT deducted. See Net Revenue (after refunds) for the post-refund figure. |
| Refunds | NOT deducted. Refunds live on a separate /refunds collection in Viva’s API and are tracked by viva_refund_value. A fully refunded EUR 100 transaction still contributes EUR 100 here. |
| Disputes / chargebacks | NOT deducted. Disputes (/disputes endpoint) are tracked separately. A successful charge later disputed still counts here. |
| Failed / declined payments | Excluded. Only StatusId = F (Successful) rows are summed. E (Error), X (Cancelled), M (Maximum number of payment attempts reached) are excluded and counted in viva_decline_rate. |
| 3DS 2 treatment | Both frictionless and challenge-completed flows count here. 3DS challenges that the customer abandoned end as StatusId = X and are excluded; abandonment is tracked separately in viv_threedsecure_abandon_rate. |
| Recurring vs one-time | Both included. Viva Recurring Payments (token-based card-on-file rebills) and one-time Smart Checkout sessions are both Type = Capture and both contribute. |
| Channels | Online + POS unified. Viva’s distinguishing feature is omnichannel reporting in one feed. POS terminal captures (Smart POS Android), e-shop checkouts, and pay-by-link transactions all flow through the same API. |
| Payout timing | Per transaction date (when the customer paid), NOT per payout date (when Viva transferred to your bank). Viva-issued IBAN accounts can settle within minutes (instant transfer); non-Viva IBAN accounts settle T+1 to T+3 via SEPA. See viv_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 |
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 Greek SMB retailer (“Aegean Apparel”) runs three Athens stores plus a pan-EU e-shop on Viva. The 30-day window covers 03 Apr 26 to 02 May 26.| Channel | Transactions | Amount | Currency | StatusId | Notes |
|---|---|---|---|---|---|
| Athens flagship Smart POS | 2,140 captures | EUR 184,300 | EUR | F | Card-present, mostly debit |
| Thessaloniki Smart POS | 980 captures | EUR 71,400 | EUR | F | Card-present |
| Piraeus Smart POS | 620 captures | EUR 38,900 | EUR | F | Card-present |
| Online e-shop, Greek customers | 1,810 sessions | EUR 142,500 | EUR | F | Smart Checkout, 3DS 2 frictionless 78% |
| Online e-shop, French customers | 340 sessions | EUR 28,200 | EUR | F | Smart Checkout, EUR settlement |
| Online e-shop, UK customers | 220 sessions | GBP 22,800 | GBP | F | Settled in GBP, no FX needed |
| Online e-shop, Romanian customers | 95 sessions | RON 41,300 | RON | F | Settled in RON, lei-denominated |
| Refunds (period) | 78 refunds | EUR 6,400 | EUR | - | Tracked separately |
| Disputes (period) | 4 cases | EUR 580 | EUR | - | Tracked separately |
| Failed / abandoned | 412 attempts | - | - | E / X | Excluded |
- POS and online unified. Aegean Apparel’s owner sees a single EUR 465,300 figure that combines three physical stores and the e-shop. On Stripe or Adyen this would normally require splitting POS-card-present from online-card-not-present manually. Viva treats them as the same
Type = Capturerail. - Three currencies displayed side-by-side, not converted. A merchant looking for a single “rolled-up EUR equivalent” will not find it on this card; that conversion lives in
viva_revenue_by_countrywhich uses Viva’s published daily FX. This is intentional, FX-converted totals are misleading for a payment institution where settlement actually happens in the native currency. - 3DS 2 frictionless rate of 78% on online traffic. PSD2 SCA is mandatory for EEA card payments above EUR 30; Viva’s Smart Checkout achieves “frictionless” (no challenge) on 75, 80% of eligible traffic by feeding strong device + transaction risk data to the issuer. The 22% that get a challenge are tracked in
viv_threedsecure_abandon_rate, abandon rates of 8, 12% on challenge are normal. - The 0.8, 1.4% fee bracket. EU intra-EEA debit cards are capped at 0.2% interchange and credit cards at 0.3% under the IFR. Viva typically prices Greek + Mediterranean SMBs in the 0.8, 1.2% blended range, materially below Stripe’s 1.4% + EUR 0.25 list price for EEA cards. This is the single biggest reason Mediterranean SMBs adopt Viva over Stripe.
- Settlement in minutes for Viva-IBAN accounts. Aegean Apparel banks with Viva’s own electronic-money IBAN, so most online transactions settle to the merchant balance within minutes (instant rail) and POS settles end-of-day. If they used a third-party bank, settlement would be SEPA T+1 to T+3.
Sibling cards merchants should reference together
| Card | Why merchants reach for it next to Total Revenue |
|---|---|
viva_net_revenue | Same metric minus refunds, the closer-to-P&L view |
viva_revenue_trend | This metric trended daily over the window |
viva_revenue_by_country | The unambiguous per-country breakdown when this card sums multiple currencies |
viva_total_transactions | Transaction count over the same window. Revenue ÷ transactions = average transaction. |
viva_avg_transaction | The per-transaction view, the denominator-aware reading. |
viva_refund_value | The amount to subtract for a net-of-refunds figure. |
viva_pending_payouts | What’s in flight from this revenue but not yet in 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 | The upstream commerce view. Viva should reconcile to (commerce_total minus non-Viva-payment-method orders). |
Reconciling against the vendor’s own dashboard
Where to look in the Viva Payments Dashboard: Sign in at viva.com/business/account/login and the closest comparable view is:Viva Business → Sales → Transactions (filter by date range; “Status: Successful”)The headline tile on the Sales overview also shows period revenue. For the omnichannel breakdown, use Sales → Reports → Channels which separates online checkout, Smart POS, recurring, and pay-by-link. Other Viva views that look similar but answer different questions:
- Settlements view (Sales → Settlements). This is post-reserve, post-fee settled balance, NOT gross transaction volume. Always lower than this card. Use
viva_net_revenueand Viva’s effective fee rate to bridge. - Disputes view (Sales → Disputes). Tracks chargeback / dispute cases, not transaction volume.
- Marketplace Splits view (Business → Marketplace, where enabled). For platform merchants splitting payments to sub-merchants, this view shows the platform’s residual after splits, not gross marketplace volume.
- Smart POS terminal reports (Devices → Terminals). Per-terminal end-of-day reports. These are a subset of this card (POS-only, one device).
| Reason | Direction | Why |
|---|---|---|
| Time zone | Boundary days off | Viva Dashboard renders in your account’s configured timezone (Greek merchants default to Athens EET / EEST, UK merchants to Europe/London). 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 (Athens is UTC+2 / UTC+3). |
| Settlement-period reserves | Theirs lower (Settlements view) | Viva can hold a small reserve on new merchants or seasonal businesses; the Settlements view nets this off. This card is gross of reserves. |
| 3DS challenge state | Ours stable, theirs may move retroactively | A 3DS challenge that the customer completes hours later (some issuers extend the window) flips from “pending” to StatusId = F. Our snapshot captures whatever state was live at sync; the Viva Dashboard updates retroactively. The gap closes within 24 hours. |
| Multi-currency arithmetic | Ours is multiple currencies stacked, Viva Dashboard offers FX-converted view | Viva Dashboard offers a “Total in EUR equivalent” toggle using the day’s published FX. This card sums each currency separately. For an FX-rolled view see viva_revenue_by_country. |
| API rate limits | Ours lower for very high-volume merchants | Viva’s Payments API caps at typically 10 requests/sec on production. For merchants doing tens of thousands of transactions/day, the engine paginates at 100 transactions per page; if a sync window is interrupted, the most recent transactions may be deferred to the next refresh. |
| Refresh lag | Ours lower for “today” | Our index updates on a periodic sync; the most recent 5, 15 minutes of transactions may not be in yet. Yesterday and earlier are fully caught up. |
| Comparison | Expected relationship | When divergence is legitimate |
|---|---|---|
viva_total_revenue ↔ shopify.total_revenue | viva ≤ shopify | Shopify includes orders paid via Stripe, PayPal, Apple Pay direct, Klarna, gift cards, manual bank transfer, none of which touch Viva. For a Mediterranean Shopify store using Viva as primary processor, expect Viva to cover 70, 95% of online revenue. |
viva_total_revenue ↔ bigcommerce.total_revenue | viva ≤ bigcommerce | Same logic. BC supports many gateways; each one displaces Viva revenue. |
viva_total_revenue ↔ adobe_commerce.total_revenue | viva ≤ adobe_commerce | Same logic. Adobe Commerce stores in Greece often run Viva alongside legacy gateway. |
viva_total_revenue + 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. Both Viva and Stripe are subsets of the commerce total; they should never exceed it. If they do, there’s likely double-counting (e.g. 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 Viva Dashboard / my bank?”) are answered in the Reconciling against the vendor’s own dashboard section above. Below are the questions that aren’t reconciliation.“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 take majority control), but day-to-day operations, the Viva Business Dashboard, the Smart Checkout API, Smart POS terminals, settlement rails, fee structures, and licences as a regulated electronic-money institution 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 a workflow change. KPIs in this card are unaffected. “Why is Viva often cheaper than Stripe for my Greek / Mediterranean store?” Three reasons. (1) IFR cap. EU intra-EEA debit interchange is capped at 0.2%, credit at 0.3%. Viva typically passes more of this saving through to SMBs in Greece, Cyprus, Spain, Italy, Portugal, Romania than Stripe does. Stripe’s blended SMB rate for EEA cards (1.4% + EUR 0.25) builds in a margin Viva can undercut for local issuers. (2) Local issuer routing. Viva has direct connections to Greek and Cyprus issuing banks, no extra acquirer hop. Stripe’s traffic for Greek issuers often routes via a non-Greek acquiring relationship, which adds basis points. (3) Greek-language support and on-the-ground POS hardware, structurally cheaper for the merchant to operate. “Does Viva settle natively in multiple currencies, or convert everything to EUR?” Viva natively settles in 13+ currencies (EUR, GBP, RON, CHF, USD, BGN, HRK, HUF, PLN, CZK, DKK, NOK, SEK) 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, which is materially cheaper than the Stripe model where everything either converts to your home currency at Stripe FX (1% spread) or sits in a Stripe Treasury balance. This card respects native settlement, you’ll see EUR + GBP + RON listed alongside each other, not converted. Use
viva_revenue_by_country for the FX-rolled view.
“3DS 2 frictionless rate, what’s a good number?”
75, 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 (typically a misconfigured MerchantTrxId or missing browser data); above 90% suggests you’re in the issuer’s “trusted-merchant” allowlist, which is excellent. Track this in viv_threedsecure_abandon_rate.
“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 which separates e-commerce from physical. We’re publishing a per-channel split (online vs Smart POS vs recurring vs pay-by-link) as a separate card; in the meantime use the Viva Dashboard’s Sales → Reports → Channels view for the split.
“What’s the difference between a refund and a chargeback in Viva?”
A refund is merchant-initiated (you decide to return funds via POST /api/transactions/{id}/refunds or in the Dashboard); the customer agrees, no Visa/Mastercard fees beyond a small refund processing charge. A chargeback is buyer-initiated through their issuing bank, regulated by Visa/Mastercard rules, and incurs scheme fees (~EUR 15, 25 per case) plus the disputed amount being held until resolution. Refunds are tracked in viva_refund_value; chargebacks in viv_chargeback_rate. High refund rate often prevents chargebacks, customers refunded promptly rarely escalate.
“What about Viva’s API rate limits?”
Production tier: typically 10 requests/sec, 600/min, with bursts permitted. For very high-volume merchants (>50,000 transactions/day) the engine batches reads to stay under cap; the practical effect is a 5, 15-minute lag on the freshest transactions in this card. If you’re consistently above the rate limit, contact Viva merchant support for a tier upgrade.
“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, both contribute. Track them separately via the RecurringTransactionId field; a dedicated Subscription Revenue card is on the roadmap.
“Why is the customer-paid total higher than what arrived in my Viva merchant balance?”
Three deductions between this card and your IBAN: (1) Viva’s blended fee (typically 0.8, 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 Viva Net Revenue and the Settlements view together to bridge.