At a glance
The count of successful transactions on Viva Payments rails in the period: how many discrete charges hit the rail, regardless of size. The denominator behind average-transaction value, decline-rate, refund-rate, and 3DS-abandon-rate. Volume’s twin metric.
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 Cypriot pharmacy chain (“Aphrodite Pharma”) runs four high-street stores plus an online prescription-fulfilment site. Window 03 Apr 26 to 02 May 26.- POS is 86.8% of transaction count but 76% of revenue. Pharmacy traffic is volume-heavy and ticket-light; finance-team revenue dashboards under-represent the operational load that POS terminals carry. Counting transactions exposes throughput pressure that revenue alone hides.
- Pay-by-link is 0.2% of count but contributes 1.2% of revenue. 32 captures at EUR 480 average is a small flow but a high-margin one. CFOs reviewing volume-only dashboards can miss the strategic value of B2B payment rails.
- Recurring at 720 rebills implies ~720 active subscribers. Rebill count is an immediate proxy for active subscription base. A 5% drop month-on-month is a churn signal worth investigating in the upstream subscription tool before the revenue impact lands.
- Online ticket EUR 48 is 2x POS ticket. Online basket-builders add multiple items; in-store traffic buys impulse OTC. This is normal pharmacy behavior. A reversal would be unusual.
- Per-store transaction count is the staffing signal. Nicosia at 4,820 captures over 30 days is roughly 160 transactions/day, well within one cashier’s throughput. Anything above 250/day suggests a second register is needed at peak hours.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in the Viva Payments Dashboard: viva.com/business/account/login. Closest comparable view:Viva Business → Sales → Transactions (filter “Status: Successful”; the row count at the bottom = this card)The Sales overview page also shows a “Successful transactions” tile. Other Viva views:
- Smart POS terminal reports (Devices → Terminals): per-device transaction counts; subset of this card.
- Recurring (Subscriptions) view: rebill counts; subset of this card.
Cross-connector reconciliation:
Known limitations / merchant FAQs
“Why does this card differ from my Shopify / BC orders count?” A few reasons. (1) Multi-charge orders: Shopify orders paid via deposit + remainder, partial captures, or subscription installments produce multiple Viva transactions per order. (2) Authorisation-only flows: a Shopify order with manual capture later doesn’t count here until captured. (3) Channel mix: the commerce platform counts orders paid by any method; Viva only sees Viva-routed orders. “Are 3DS-abandoned attempts in this count?” No. OnlyStatusId = F counts. Abandons are X, declines are E or M. To see the full attempt funnel, pair this card with viv_decline_rate and viv_threedsecure_abandon_rate.
“Recurring rebills, do those add up here?”
Yes. Each successful rebill is one transaction. Failed rebills go to declines, retries that succeed flip back to successful and count.
“Multi-currency, does count work the same way?”
Yes. Count is currency-neutral. One EUR transaction and one GBP transaction both add 1.
“Pay-by-link, are those in here?”
Yes. Pay-by-link transactions are Type = Capture once the customer pays the link. They count uniformly with online checkout and POS.
“Why are POS counts so high relative to online?”
For physical retail (pharmacy, grocery, food, fashion-flagship), POS volume is structurally 5 to 20x online by transaction count. Online tickets are higher; POS tickets are lower; the per-channel split tells you where to look for throughput pressure.
“Smart Retry on a failed rebill, does the original failure stay in the metric?”
The failure is in declines historically (E then). When Smart Retry succeeds 3 to 7 days later, the new attempt is F and adds to this count. The historical decline doesn’t move backward.
“My JP Morgan acquisition concern, anything affecting transaction counts?”
No. Transaction recording, status lifecycle, and API behaviour are unchanged post-acquisition.