> ## 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. # Revenue Over Time, Viva Payments > Revenue Over Time for Viva Payments stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained) • **Category:** [Payment Gateway](/nerve-centre/connectors#connectors-by-type) ## At a glance > Daily series of [`viva_total_revenue`](/nerve-centre/kpi-cards/viva-payments/total-revenue). Surfaces day-of-week patterns, paydays, weekends, sales events, and anomalies that summary-card numbers hide. | | | | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | **What it counts** | `SUM(transactions.Amount WHERE StatusId = F)` bucketed by day, in each transaction's `CurrencyCode`. Multi-currency stores get one trend per currency. | | **API endpoint** | [`/api/transactions`](https://developer.vivawallet.com/apis-for-payments/payment-api/) aggregated by `InsDate` (UTC day). | | **Currency** | Multi-currency native, no FX. Per-currency lines stacked. | | **Refunds / disputes** | NOT deducted (gross daily revenue). Use [`viva_refunds_trend`](/nerve-centre/kpi-cards/viva-payments/refunds-over-time) for the deduction trend. | | **Failed / declined payments** | Excluded. | | **Channels** | Online + POS unified. Channel split available via filter (`SourceCode`). | | **3DS late completion** | A challenge completed late in UTC may land on the next day's bucket; small drift on day-boundary. | | **Time window** | `90D rolling` (default). | | **Alert trigger** | `revenue_trend` `sentiment_key` flags daily anomalies (>2σ deviation from rolling mean). | | **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 omnichannel retailer ("Ouzeri Supplies") on Smart Checkout + 4 Smart POS. 90-day window 02 Feb 26 to 02 May 26. ```text theme={null} Daily revenue (EUR), 02 Feb 26 to 02 May 26 Mon | XXXXXXXXXXXXXX ~ EUR 3,800 Tue | XXXXXXXXXXX ~ EUR 3,200 Wed | XXXXXXXXXXX ~ EUR 3,100 Thu | XXXXXXXXXXX ~ EUR 3,400 Fri | XXXXXXXXXXXXXXXXXXXX ~ EUR 5,800 Sat | XXXXXXXXXXXXXXXXXXXXXXXX ~ EUR 7,200 Sun | XXXXXXXXX ~ EUR 2,600 Greek-Easter spike (12-14 Apr 26) EUR 28,400 in 3 days (+520% vs avg) Orthodox-Easter Monday (13 Apr 26) Public holiday, low POS, online flat Spring Sale (28 Apr 26) EUR 18,200 single day (+390% vs avg) ``` What the merchant should notice: 1. **Saturday is the peak.** Athens Saturday foot-traffic on top of online weekend browsing produces the biggest day. Greek Sunday is the quietest day, many small businesses closed for trading by tradition. 2. **Greek-Easter (12, 14 Apr 26) is a 3-day spike, not single-day.** Orthodox Easter is the largest commerce moment in Greek retail. The trend chart shows the lift starting Friday (food shopping for Sunday lunch). 3. **Easter Monday is a public holiday.** Smart POS volume drops to near-zero (stores closed); online stays flat. If your blended trend dips on Easter Monday, this is structural, not a problem. 4. **Spring Sale single-day spike (28 Apr 26)** is the typical "one-day-flash" pattern. Compare the spike day's transaction count and avg transaction to a normal day, did you sell more units, or did you just discount the same units? The trend on its own can't tell you; pair with [`viva_total_transactions`](/nerve-centre/kpi-cards/viva-payments/successful-transactions) and [`viva_avg_transaction`](/nerve-centre/kpi-cards/viva-payments/average-transaction). 5. **Multi-currency stores see multiple trends stacked.** EUR line is the bulk; GBP line is a smaller separate stream visible in the same chart but read as a separate currency. ## Sibling cards merchants should reference together | Card | Why pair it with Revenue Trend | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | | [`viva_total_revenue`](/nerve-centre/kpi-cards/viva-payments/total-revenue) | The summary number; this card is its time-series. | | [`viv_volume_trend`](/nerve-centre/kpi-cards/viva-payments/volume-trend) | Same time-axis, transaction count. Combine to read avg-transaction trend. | | [`viva_refunds_trend`](/nerve-centre/kpi-cards/viva-payments/refunds-over-time) | Refund time-series; subtract from this for net trend. | | [`viva_total_transactions`](/nerve-centre/kpi-cards/viva-payments/successful-transactions) | Transaction-count summary. | | [`viva_avg_transaction`](/nerve-centre/kpi-cards/viva-payments/average-transaction) | Per-transaction view. | | [`viva_payment_methods`](/nerve-centre/kpi-cards/viva-payments/payment-methods) | When trend moves, method-mix often drives it. | | Stripe [`stripe_revenue_trend`](/nerve-centre/kpi-cards/stripe/revenue-over-time) / PayPal [`pp_revenue_trend`](/nerve-centre/kpi-cards/paypal/revenue-over-time) | Cross-PSP comparison. | | Commerce platform total revenue trend | Upstream view. Discrepancies between Viva and commerce-platform trend usually indicate a non-Viva-method spike or refund timing. | ## Reconciling against the vendor's own dashboard **Where to look in the Viva Payments Dashboard:** [viva.com/business/account/login](https://www.viva.com/en/business/account/login). Closest comparable view: > **Viva Business → Sales overview** (line chart, period selector top-right; "Daily" granularity) The **Reports → Net Sales** view also exposes a chart of net daily revenue (post-refund). **Why our number may legitimately differ from the Viva Dashboard:** | Reason | Direction | Why | | ----------------------- | ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Time zone bucketing** | Day boundaries shift | Viva buckets by account timezone (Athens EET / EEST = UTC+2/+3); we use UTC. A late-evening Athens transaction lands in tomorrow's UTC bucket but today's Athens bucket. For "today" / "yesterday" cards this can move material amounts; for 90-day rolling averages the effect is small. | | **Multi-currency** | Ours per-currency, theirs may roll | FX-rolled view available in Viva Dashboard. | | **3DS late completion** | Day-boundary drift | A challenge completed late in the day may land on the next bucket. | **Cross-connector reconciliation:** | Comparison | Expected relationship | When divergence is legitimate | | -------------------------------------------------------------------------------------------------------- | ------------------------- | ------------------------------------------------------------------------------------------------------------------ | | `viva_revenue_trend` ↔ commerce-platform daily revenue | Daily shapes should match | If commerce-platform shows a spike that Viva doesn't, it's a non-Viva-method spike (PayPal sale, Klarna campaign). | | `viva_revenue_trend` ↔ [`stripe.stripe_revenue_trend`](/nerve-centre/kpi-cards/stripe/revenue-over-time) | Independent | Two streams summed approximate the commerce platform trend. | ***
Documentation cross-reference (same archetype on other PSPs) * [`stripe.stripe_revenue_trend`](/nerve-centre/kpi-cards/stripe/revenue-over-time) * [`paypal.pp_revenue_trend`](/nerve-centre/kpi-cards/paypal/revenue-over-time)
## Known limitations / merchant FAQs **Why does the chart not match my Viva Dashboard chart day-for-day?** Time-zone bucketing. We use UTC; Viva Dashboard uses your account timezone. For Greek merchants this is a 2, 3 hour offset, transactions late at night Athens-time land in the next UTC day. Aggregate views (7-day, 30-day) match; individual days can shift. **There's a single-day spike, what's likely?** Top causes: (1) sale or promotion, (2) a single very-large B2B / wholesale transaction, (3) a recurring rebill batch fired (some Viva merchants set rebill day on the 1st of the month, creating a day-1 spike), (4) a fraud-related test where many small transactions ran in minutes (rare but worth checking). **My weekend dip is normal?** Greek and Mediterranean retailers often see Sunday as the lowest day (cultural). Northern European stores see Saturday-Sunday combined as the highest. Trend shape depends on customer geography. **Easter, Christmas, Greek bank holidays, do they show?** Yes, public holidays show structurally lower POS volume (stores closed) and roughly-flat online. Greek-Easter is the largest commerce moment in Greek retail, similar in scale to UK Christmas. **Can I filter to online-only?** Use the `SourceCode = e-commerce` filter (or `physical` for POS) in the Viva Dashboard. The card's default is blended. **Multi-currency view, what do I see?** Per-currency lines stacked on the same chart. Don't read the EUR line as the total if you also take GBP, GBP is shown separately. **JP Morgan ownership, trend changes?** None. Trend mechanics, sync cadence, and bucketing unchanged. **Why is yesterday's bucket lower than today's halfway through the day?** Refresh lag. The most recent few minutes of transactions haven't synced. By next refresh, today's bucket catches up. *** ### Tracked live in Vortex IQ Nerve Centre *Revenue Over Time* is one of hundreds of KPI pulses Vortex IQ tracks across Viva Payments and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.