Total Transaction Value, CyberSource

​

At a glance

The total amount that successfully flowed through CyberSource in the period, gross of refunds, gross of interchange / acquirer fees, gross of disputes. This is “money that touched our enterprise gateway”, not “money we kept”. Authoritative source for finance teams reconciling daily processing volume to bank settlements; should be the largest payment-volume number on the board pack for any CyberSource-primary merchant.

​

Calculation

​

Worked example

Total Transaction Value (this card)
  = $312.4M + €68.2M + £24.8M + C$11.6M
    (no FX conversion, summed in presentment currency)

Net Revenue (after refunds + fees)             ≈ $312.4M − $4.2M refunds − ~$8.7M fees  ≈ $299.5M (USD only)
Total kept after disputes lost                 ≈ $299.5M − $1.1M lost disputes          ≈ $298.4M
USD-normalised view (FX at period close)       ≈ $312.4M + $74.3M + $30.9M + $8.6M       ≈ $426.2M

1. Multi-currency arithmetic is a frequent surprise. Finance teams expect a single USD-equivalent figure on the board pack, but the engine sums each currency in its own units to preserve the audit trail. The Revenue by Currency card is the unambiguous breakdown; the FX-normalised view is a manifest toggle that finance can request.
2. Decision Manager REVIEW is excluded by design. 38,100 transactions sat in DM REVIEW for this period. Of those, ops manually approved ~31,400 within 4 hours (the operating SLA), which then re-submitted as fresh /tss/v2/searches calls and authorised. Those re-authorisation transactions ARE in the AUTHORIZED count. The 6,700 that ops never approved (or that customers abandoned during review) are correctly excluded.
3. Tokenization carrying the auth rate. 78% of this hotel group’s transactions came from CyberSource Token Management Service (corporate-account billing, repeat guest profiles, OTA partner integrations). TMS-tokenized auth rate ran 96.8% vs fresh-card 91.2%. The blended ~94.4% reflects the heavy TMS skew; if the merchant suddenly took more direct-fresh-card traffic (e.g. switched OTAs), this card’s growth rate would slow even with stable booking volume.
4. Cross-border share matters for the dispute-rate denominator. 23% of authorised volume was cross-border (card-issuing-country ≠ merchant-billing-country). Cross-border transactions have higher chargeback rates (typically 1.5, 2x the domestic rate) so the dispute denominator built off this card carries more risk per dollar than a pure-domestic merchant would. See Cross-Border Transaction Share.
5. PARTIAL_AUTHORIZED excluded (correctly). A PARTIAL_AUTHORIZED outcome means the issuer authorised a smaller amount than requested (typical on prepaid cards near balance limit, or on travel-booking gift-card splits). The hotel ops team typically captures the partial amount and seeks alternate tender for the balance; that re-submission flows through as a separate AUTHORIZED. Counting partial-auth here would double-count revenue. EBC2 surfaces partial-auth in its own bucket.

​

Sibling cards merchants should reference together

​

Reconciling against the vendor’s own dashboard

• Reports → Standard Reports → Conversion Detail Report, the daily transaction-level dump for finance reconciliation. This is the source of truth for “what did our gateway authorise yesterday”.
• Reports → Payment Batch Detail Report, the settlement-batch view (what arrived at the acquirer’s bank account). This will be lower than this card by gateway fees, interchange, and any held / disputed transactions.
• Decisions → Decision Manager → Performance Reports for the ACCEPT vs REVIEW vs REJECT split feeding the AUTHORIZED count.

​

Known limitations / merchant FAQs

Reconciliation questions (“why doesn’t this match EBC2 / my bank?”) are answered in the Reconciling against the vendor’s own dashboard section above. Below are the merchant questions that aren’t reconciliation.

• Quarterly Decision Manager rule pack rollouts. Fraud-ops teams typically deploy DM rule changes on a quarterly cadence; a too-aggressive rule can cut authorisations 5, 12% within a single quarter. Check Decision Manager Score Mix before assuming traffic loss.
• Cross-border FX shifts. EUR/USD or GBP/USD moving >5% within a period changes both demand (consumer side) and authorisation rates (issuer-side credit-line tightening on weakening currencies). Watch Revenue by Country and Decline Rate by Card-Country.
• Token Management Service expiration cliffs. When a large cohort of stored tokens expires simultaneously (e.g. all the cards stored during a Q4 holiday push expire 12 months later), the recurring-billing book sees a temporary auth-rate dip. See Stored-Token Health.

​

Tracked live in Vortex IQ Nerve Centre