> ## 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. # Average Transaction, Helcim > Average Transaction for Helcim 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 > Average successful transaction value across Helcim rails (Helcim Online + Smart Terminal + Recurring + virtual terminal). The denominator-aware reading of revenue: useful when total volume is steady but ticket size is drifting up or down. | | | | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | `SUM(amount WHERE status='APPROVED' AND type IN ('purchase','capture')) ÷ COUNT(*)` over the window, per currency. | | **API endpoint** | [`GET /v2/card-transactions`](https://devdocs.helcim.com/) on Helcim API v2. | | **Pricing model** | Helcim's interchange-plus markup is per-transaction (flat fee + percentage). Average ticket size affects effective rate: smaller tickets pay disproportionately more in per-transaction fees, larger tickets pay less. A drifting average ticket therefore shifts your effective rate even if interchange-plus terms haven't changed. | | **Currency** | **Per-currency, no FX.** CAD-only, USD-only, or both displayed separately. A CAD merchant accepting USD will see CAD avg and USD avg as separate rows. | | **Refunds** | Refunds excluded from numerator and denominator. | | **Disputes** | Disputes still included (the original capture was successful). | | **Failed / declined** | Excluded. Only `APPROVED` rows count. | | **3DS abandons** | Excluded (those captures never completed). | | **Channels** | Online + POS + Recurring blended. POS and recurring typically pull the average up (POS tickets tend to be larger for retail; recurring is fixed-amount); pure-online may pull it down depending on category. The per-channel split lives in `hel_top_payment_methods`. | | **Time window** | `30D vsP` (default). | | **Alert trigger** | `±20%` move vs prior period (move in either direction is flag-worthy). | | **Roles** | owner, finance, operations | ## Calculation Calculated automatically from your Helcim 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 representative reading of **Average Transaction** for a typical merchant on Helcim.* The card reports the current period value alongside a comparison against the previous period. Direction matters: rising values may be healthy or concerning depending on the underlying metric. Cross-reference the siblings below to triangulate cause when the value moves outside expected range. For deeper investigation, use Vortex Mind to trace upstream causes; for natural-language exploration, ask Ask Viq. ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | ------------------------------------------------------------------------------- | ----------------------------------------------- | | [`hel_total_transactions`](/nerve-centre/kpi-cards/helcim/total-transactions) | Volume sibling: Total Transactions. | | [`hel_total_volume`](/nerve-centre/kpi-cards/helcim/total-volume) | Volume sibling: Total Volume. | | [`hel_volume_trend`](/nerve-centre/kpi-cards/helcim/volume-trend) | Volume sibling: Volume Trend. | | [`hel_avg_settlement_days`](/nerve-centre/kpi-cards/helcim/avg-settlement-time) | Settlement sibling: Avg Settlement Time (days). | | [`hel_chargeback_rate`](/nerve-centre/kpi-cards/helcim/chargeback-rate) | Refunds & Disputes sibling: Chargeback Rate. | ## Reconciling against the vendor's own dashboard **Where to look in Helcim's own dashboard:** The Helcim dashboard surfaces this metric (or its components) under the relevant report section. Confirm period boundaries and filter settings match the Vortex IQ profile to reconcile cleanly. **Why the Vortex IQ value may legitimately differ:** | Reason | Direction | What to do | | ---------------------------------------------------------------------------------------------------------- | --------- | ------------------------ | | **Period boundary.** Vortex IQ uses 30-day rolling by default; vendor dashboards may use calendar periods. | Variable | Match the period range. | | **Time zone.** Vendor uses account time zone; Vortex IQ aligns to merchant reporting time zone. | Marginal | Confirm time zone match. | | **Filter scope.** Profile-level filters (channel, B2B, test orders) may narrow the Vortex IQ view. | Variable | Match filter settings. | **Cross-connector reconciliation:** complement with sibling cards in the same category for the full diagnostic picture. For divergence investigations, use Vortex Mind. ## Known limitations / merchant FAQs **Q: How often does Average Transaction update?** The card refreshes on the standard data refresh (typically every 30-60 minutes for live integrations). For real-time signals, force a manual refresh from the dashboard. **Q: Why does my Helcim dashboard show a different number?** The most common reasons are period-boundary differences (Vortex IQ uses 30-day rolling vs vendor's calendar months), time-zone alignment, and filter scope (profile-level vs vendor's all-account view). Match these settings before assuming a real divergence. **Q: How does Average Transaction relate to other volume metrics?** Track this card alongside the siblings listed above to build a complete picture. Single-metric reads can mislead; the diagnostic value is in the cross-reference. **Q: Can I customise the alert threshold?** Yes, alert thresholds are configurable per profile in the Alert Rules tab. Adjust to match your business baseline rather than relying on the generic default. *** ### Tracked live in Vortex IQ Nerve Centre *Average Transaction* is one of hundreds of KPI pulses Vortex IQ tracks across Helcim 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.