At a glance
Successful Viva Payments revenue grouped by customer country (or, when missing, card-issuer country). The cross-border / domestic split that’s structurally important for pan-EU SMBs adopting Viva for multi-country expansion.
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 pan-EU DTC olive-oil brand (“Aegean Olive”) shipping to 12 EU countries, headquartered Greece. Window 03 Apr 26 to 02 May 26.- Greece + Cyprus = 53% of revenue. Mediterranean home-market dominance is normal for a Greek brand. If this drops, either home market is shrinking or international growth is real, watch the trend.
- Germany at 14% with no German-language site is impressive. A brand selling to DE customers in English/Greek is leaving conversion on the table; native-language checkout typically lifts DE conversion 15, 25%.
- GBP-settled revenue at EUR 28,300 equivalent is ~6%, with FX applied at 1.17. UK customers paying in GBP avoid Stripe-style 1% FX spread; the merchant settles directly to a GBP IBAN with Viva. A pan-EU brand serving UK is structurally cheaper on Viva than on Stripe for this reason.
- RON traffic is small but present. Romanian customers pay in lei; Viva natively settles to a RON IBAN (or converts to EUR daily at published rate). Most non-Greek competitors don’t offer RON settlement and lose Romanian customers to local PSPs.
- “Other” at 1% covers tail markets. Often Spain (ES), Portugal (PT), Bulgaria (BG), Sweden (SE), Norway (NO). Each individually small but worth aggregating for marketing planning.
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 → Reports → GeographyThe map view shows revenue density by country; the table view exposes per-country totals. Why our number may legitimately differ from the Viva Dashboard:
Cross-connector reconciliation:
Known limitations / merchant FAQs
Why is “Unknown” not zero? Some transactions arrive without billing country (guest checkout, certain wallet flows). We fall back to BIN-derived card country, which covers most. Residual “Unknown” is typically <2%; if higher, your checkout is missing a billing address requirement. Multi-currency settlement, does this card show native or EUR? Default presentment is EUR (or your account’s home currency). Hover any country row for the native amount. The FX is Viva’s published daily rate. Why is my UK-share lower than my Shopify UK-share? UK customers paying with PayPal don’t appear here. Sumpaypal.pp_revenue_by_country UK + this card’s UK + any Stripe UK to triangulate.
Greek customers paying with Greek-issued card vs non-Greek card?
Customer billing country is Greek (resolves to GR) regardless of card. Card-country only used when billing is missing. The mismatch view is viva_card_country_mismatch.
Romanian customers paying in lei (RON), do they show in Romania row?
Yes, billing-country = RO; native amount = RON; presentment EUR-converted at day-rate.
Customer in Cyprus paying in EUR, vs Greek customer paying in EUR?
Both EUR-native. The country split is by billing country, not currency. Cyprus = CY row; Greece = GR row; both denominated EUR.
My country share moved 5pp, what to investigate?
Marketing campaign launched in that country, currency / FX shift made one country relatively cheaper, public holiday in home market, or a competitor outage in target market. Cross-reference viva_revenue_trend for daily timing.
JP Morgan ownership impact?
None.