Net Payment Volume

Overview

Net payment volume summarizes economic payment activity retained after defined deductions. A provider may start with authorized, captured, or settled payment value and subtract refunds, reversals, chargebacks, internal tests, or other categories according to its reporting methodology.

The metric is not standardized across companies. Some reports exclude fees or failed transactions, while others net only refunds. Currency conversion, timing, marketplace pass-through, duplicate events, and stablecoin price movement can affect totals. It should not be treated automatically as revenue.

Reports should publish the calculation, payment stage, exclusions, currency rates, and period cutoffs. Operations teams should reconcile source transactions through authorization, capture, settlement, refund, dispute, and payout states. Comparisons require identical definitions and consistent handling of internal or canceled activity.

Operational use of Net Payment Volume requires a consistent record of eligible population, reporting period, transaction stage, amount or count basis, currency conversion, exclusions, corrections, and source lineage. The record should preserve the original observation and later corrections so finance, operations, and support teams can explain the outcome from the same evidence.

Net Payment Volume can appear in the same workflow as payment volume and authorization, but the records should remain separately identifiable. A relationship between them does not prove that pricing, execution, settlement, custody, or accounting has completed.

The scope of Net Payment Volume should preserve its defining condition: Net Payment Volume must define its eligible population, numerator, denominator or aggregation basis, time period, currency conversion, status cutoff, retries, refunds, and exclusions. Teams should document when that condition begins, which event changes it, and what evidence shows that execution, settlement, or measurement is complete. This added control specifically concerns processed payment value after subtracting specified reversals, refunds, chargebacks, or other exclusions from gross transaction value.

Control evidence for Net Payment Volume should cover eligible population, period, currency basis, transaction stage, exclusions, corrections, and source lineage. The definition also indicates that for reliable use, teams should record eligible population, reporting period, transaction stage, amount or count basis, currency conversion, exclusions, corrections, and source lineage. Keeping these details together makes later reconciliation and performance comparison possible without rewriting the original record. The record-level focus here is processed payment value after subtracting specified reversals, refunds, chargebacks, or other exclusions from gross transaction value.