Gross Payment Volume vs Net Payment Revenue
Gross Payment Volume vs Net Payment Revenue: What Merchants Actually Retain From Payments The board slide contains a green arrow: GPV +20% Last year: $100 million This year: $120 million The payments team processed another $20 million. That is unquestionably more activity. It doe
Gross Payment Volume vs Net Payment Revenue: What Merchants Actually Retain From Payments
The board slide contains a green arrow:
GPV +20%
Last year: $100 million
This year: $120 million
The payments team processed another $20 million.
That is unquestionably more activity.
It does not yet tell management whether payments created 20% more economic value.
Perhaps refunds grew faster than sales.
Perhaps fraud losses doubled.
Perhaps chargebacks became more expensive.
Perhaps the merchant entered markets with higher processing costs.
Perhaps payment operations needed additional people and manual reconciliation to support the new volume.
A payment organization can therefore report a record year for gross payment volume while the amount of value retained from each payment dollar deteriorates.
The first metric answers:
How much payment activity passed through the system?
The more useful second question is:
How much economic value remained after payment-specific leakage?
Those numbers belong beside each other.
GPV is not the same thing as revenue
Gross Payment Volume—often abbreviated GPV—is useful.
It can show the scale of payment activity and how quickly a merchant's processed business is growing.
But GPV should not automatically be called merchant revenue.
The term GPV itself does not have one universal calculation across every merchant and provider. Depending on the reporting system, teams may separately discuss:
attempted volume;
authorized volume;
captured volume;
processed volume;
completed paid value;
settled volume;
TPV;
GPV.
The brief therefore requires merchants to define whichever volume metric they actually use rather than assume “GPV” has a universal industry formula.
There is a second reason for caution.
“Revenue” carries accounting meaning.
Under IFRS 15, revenue recognition concerns contracts with customers, performance obligations, transaction price, and when promised goods or services are transferred. Payment processing activity is therefore not a substitute for an entity's accounting revenue policy.
For payment-management purposes, a merchant can create useful measures such as:
Net retained payment value
or:
Net Payment Contribution
But it should define those measures explicitly and should not imply that a newly constructed payment KPI is a GAAP or IFRS revenue measure.
Begin one stage earlier than GPV
A useful payment economics model starts before successful payment.
Consider the sequence:
Attempted value
→ Approved value
→ Completed paid value
→ Settled or collected value
→ Post-payment deductions
Each stage answers a different question.
Attempted payment value
How much value customers attempted to pay.
Be careful with retries.
If one $100 order generates three authorization attempts, simply summing raw attempts could produce $300 of “attempted value” for $100 of underlying customer demand.
Define whether the denominator represents:
unique payment intents;
authorization attempts;
orders;
individual transaction messages.
Approved value
Payment value that received successful authorization.
Approval does not necessarily prove that the order ultimately completed, captured, settled, or remained retained.
Completed paid value
Value associated with successfully completed payment or paid-order events under the merchant's chosen definition.
This is the cleanest starting point for the article's main gross-to-net payment contribution waterfall.
Settled or collected value
Value reported as settled or collected under the provider/acquirer arrangement.
Do not assume this equals GPV.
Provider reporting can apply later adjustments, netting, timing differences, or other settlement mechanics.
The most important GPV rule: write the definition down
For the rest of this illustrative article, assume the merchant defines:
GPV = completed paid value before refunds and other post-payment reductions
That is a management definition for this example, not a claim that every company uses GPV this way.
The merchant's metric dictionary should record:
Metric: GPV
Numerator: completed paid transaction value
Period: transaction/capture date
Refund treatment: gross; refunds not deducted
Chargeback treatment: not deducted
Currency normalization: specified reporting method
Included payment methods: listed explicitly
Excluded transactions: test, duplicate, void, etc.
Once that is documented, everybody can reconcile the same number.
Without it, payments, finance, data, and the PSP can all report “volume” correctly while referring to different populations.
A bigger GPV number can hide worsening economics
Use a deliberately hypothetical management report.
Metric
Year 1
Year 2
GPV / completed paid value
$100.0M
$120.0M
Refunds
$5.0M
$8.0M
Unrecovered fraud loss
$0.8M
$1.4M
Net chargeback loss
$0.7M
$1.0M
Direct payment cost
$2.8M
$3.8M
Attributable payment operations
$0.7M
$1.5M
Net Payment Contribution
$90.0M
$104.3M
All figures are illustrative.
GPV increased:
20%
Net Payment Contribution increased from $90.0 million to $104.3 million:
approximately 15.9%
So the merchant still retained more economic value in absolute dollars.
But it did not improve at the same rate as payment volume.
The retained contribution ratio moved from:
$90.0M ÷ $100.0M = 90.0%
to:
$104.3M ÷ $120.0M ≈ 86.9%
The merchant lost roughly:
3.1 percentage points of payment contribution efficiency
while celebrating 20% GPV growth.
That is exactly the kind of deterioration a gross-volume dashboard can hide.
The Gross-to-Net Payment Waterfall
The core framework is:
Attempted customer value
↓
Approved value
↓
Completed paid value
↓
minus Refunded value
minus Fraud loss
minus Net chargeback/dispute loss
minus Direct payment cost
minus Directly attributable payment operations, where included
=
Net Payment Contribution
Every line needs a definition.
That requirement is more important than the formula itself.
Step 1: attempted value
Attempted value helps quantify demand entering the payment funnel.
But it is not GPV unless the merchant explicitly defines it that way.
Suppose:
Attempted unique-order value: $128M
Approved value: $123M
Completed paid value: $120M
Then $8 million of value disappeared between payment intent and completed payment.
That is economically important.
But this article should not immediately call the $8 million:
“lost revenue.”
Some attempts may have been:
duplicate;
fraudulent;
insufficient-funds;
recovered through retry;
completed through another payment method;
abandoned for non-payment reasons.
The dedicated decline-economics article should determine what portion was actually recoverable.
Here, the waterfall simply preserves the stages.
Step 2: completed paid value
This is where the principal gross-to-net waterfall begins.
Call it GPV if that matches the organization's documented terminology.
If not, call it:
Completed Paid Value
and avoid unnecessary ambiguity.
The important thing is not the acronym.
It is a denominator that finance, payments, risk, and data can all reproduce.
Step 3: subtract refunds
A refund removes previously completed transaction value from the amount the merchant ultimately retains.
If GPV is reported gross of refunds:
Retained value before other losses
= completed paid value − refunded value
But do not immediately add every refund-related expense into this same line.
Separate:
Refunded principal
from:
refund-processing fee;
non-refundable original transaction fee;
FX effect;
fulfillment loss;
return-shipping cost.
The Hidden & Ancillary Fees cluster owns refund-fee mechanics.
This article needs only enough refund detail to quantify the effect on payment contribution.
Step 4: subtract fraud loss
“Fraud loss” also needs a scope.
Possible economic components include:
fraudulent payment value the merchant ultimately absorbs;
product/service loss;
other specifically included fraud expense.
But fraud and chargebacks overlap operationally.
A fraudulent transaction can later become a chargeback.
If finance records:
$1,000 fraud loss
and then separately records:
$1,000 chargeback reversal
for the same economic event, the waterfall has lost $2,000 from one $1,000 transaction.
That is wrong.
Choose a mutually exclusive classification policy.
For example:
Fraud loss
= fraud losses not already captured in the net chargeback-loss line.
Then keep chargebacks separate.
The brief specifically requires fraud and disputes not to be treated as synonyms.
Step 5: subtract net chargeback loss
Chargeback economics can include more than a dispute fee.
But this article should avoid reproducing the dedicated chargeback-cost analysis.
For the waterfall, define a net line such as:
Net chargeback loss
which may contain, depending on scope:
reversed payment value
plus:
included dispute charges
minus:
successful representment/recovery
Again, ensure that fraudulent chargebacks are not already counted under fraud.
The dedicated chargeback article should own goods/service loss, representment operations, fee mechanics, and recovery strategy.
Step 6: subtract direct payment cost
Now incorporate the actual cost of processing the completed payment population.
Potential inputs include:
percentage payment fees;
fixed transaction fees;
interchange/network/acquirer/PSP components where relevant;
payment-method charges;
gateway cost;
FX or settlement cost only where intentionally included;
relevant ancillary payment charges.
The scope must be stated.
The brief explicitly warns against silently mixing direct and allocated costs.
A useful metric is:
Direct payment cost rate
Direct payment cost
÷ completed paid value
If direct payment costs total $3.8 million on $120 million completed paid value:
$3.8M ÷ $120M ≈ 3.17%
That is not necessarily the merchant's quoted PSP transaction rate.
It is the effective direct payment-cost ratio using the costs intentionally placed in the numerator.
Step 7: decide whether payment operations belong in the waterfall
A lighter-weight reporting view can stop after direct payment cost.
A deeper management model may also subtract directly attributable payment operating expense.
Examples include:
payment reconciliation;
settlement exception handling;
dispute administration;
payment-provider management;
payment-specific support;
manual payment review;
payment incident operations.
Do not dump broad company overhead into the number simply because payments touch the business.
The brief recommends activity-based allocation where practical and warns against false precision from arbitrary shared-cost allocation.
If the payment operations team costs $1.5 million but half of its work relates to unrelated functions, the whole $1.5 million should not automatically enter the payment waterfall.
Define Net Payment Contribution explicitly
A practical management formula is:
Net Payment Contribution
Completed paid value
− refunded value
− unrecovered fraud loss
− net chargeback/dispute loss
− direct payment cost
− directly attributable payment operating cost, if included
This is a merchant management framework.
It is not presented as an accounting-standard definition of “net revenue.”
That distinction matters because formal revenue recognition follows the merchant's applicable accounting standards and facts. IFRS 15's framework, for example, is based on the transfer of promised goods or services and the amount of consideration the entity expects to be entitled to—not on raw payment-processing volume.
If finance prefers less ambiguous terminology, use:
Payment Contribution
or:
Net Retained Payment Value
instead of “net payment revenue.” The brief recommends exactly this discipline.
Payment contribution is still not business profit
Suppose Net Payment Contribution is $104.3 million.
That does not mean the merchant earned $104.3 million of profit.
The payment waterfall may deliberately exclude:
cost of goods;
fulfillment;
service delivery;
salaries outside payment operations;
customer acquisition;
tax;
other business expenses.
This model answers:
How much value survived the payment function's own economically relevant leakage?
It does not replace the P&L.
Gross payment volume and settled cash are different again
A merchant may also compare GPV with money arriving in its bank account.
Those numbers can diverge for reasons besides payment contribution.
That creates an important reconciliation rule:
Do not start with net payout cash and subtract refunds, chargebacks, and processing fees again if those items are already netted into the payout.
Otherwise the waterfall double counts them.
Likewise, a temporary amount withheld and expected to be released later should not automatically be classified as a permanent economic loss. It changes cash availability; whether it belongs in a separate liquidity or capital-cost model depends on the analysis being performed. This is an analytical inference from the settlement mechanics rather than an accounting conclusion.
There are two valid ways to build the waterfall
Method 1: Transaction-led
Start with:
completed paid value
Then subtract each loss and cost explicitly.
Best for:
economic analysis;
category attribution;
comparison over time;
diagnosing leakage.
Method 2: Settlement-led
Start with provider settlement/payout data.
Then reconcile backward to the gross transaction population and identify which adjustments are already netted.
Best for:
finance reconciliation;
cash matching;
verifying provider reports.
Do not mix the methods halfway through.
If the payout already deducts a refund, do not subtract the refund again.
If a fraud loss appears later as a chargeback, determine where the economic loss is actually recorded.
Why GPV growth can be economically healthy even when the contribution percentage falls
A falling contribution ratio is not automatically bad.
Suppose the merchant entered a new market where:
processing fees are higher;
refunds are somewhat higher;
but incremental completed orders create attractive product margin.
Payment contribution percentage may decline while absolute merchant profit improves materially.
This article should therefore avoid turning:
highest payment contribution percentage
into another isolated optimization objective.
The purpose of the waterfall is diagnosis.
It shows what payment activity becomes after payment-specific erosion.
Management still needs the merchant's product contribution economics to decide whether acquiring that volume was worthwhile.
Why a higher contribution percentage can also be misleading
The reverse can happen.
Suppose a merchant aggressively blocks high-risk payments.
Fraud losses collapse.
Refunds fall.
Payment contribution as a percentage of completed payments looks excellent.
But legitimate customers may also have been declined.
Because the denominator contains only completed payments, the waterfall cannot show value that never entered GPV.
That belongs upstream:
attempted value → approved value → completed value
This is why a responsible dashboard needs both:
Funnel performance
and:
Gross-to-net retention
Optimizing only one can hide deterioration in the other.
The waterfall needs mutually exclusive loss categories
A robust metric dictionary should contain a rule for each overlap.
Refund versus chargeback
If a payment was refunded before a dispute, do not later subtract the same principal twice.
Fraud versus chargeback
If fraud loss is recognized through the chargeback line, do not duplicate it under fraud.
Fees
If a provider's all-in fee already contains a network/acquirer component, do not add that component again.
Settlement
If net settlement already includes refunds and chargebacks, do not subtract them a second time.
Payment operations
If dispute staff cost is already allocated into a chargeback-specific economic model imported into the waterfall, do not also include the same labor under broad operations.
Every dollar should have one primary economic home.
A practical metric dictionary
Metric
Definition
Suggested denominator
Attempted value
Defined payment-intent or attempt value
Unique intent/order or authorization attempts
Approval rate
Approved authorizations ÷ authorization attempts
Authorization attempts
Completed paid value
Successfully completed paid value
—
GPV
Merchant-defined gross payment-volume metric
Must document
Refund rate
Refunded value ÷ comparable completed paid value
Completed paid value
Fraud-loss rate
Defined fraud loss ÷ relevant payment value
State explicitly
Net chargeback-loss rate
Net dispute loss ÷ relevant completed/settled value
State explicitly
Direct payment cost rate
Direct payment cost ÷ completed paid value
Completed paid value
Net Payment Contribution
Defined gross-to-net management value
—
Payment contribution ratio
Net Payment Contribution ÷ completed paid value
Completed paid value
The point is not to force one universal denominator on every metric.
It is to ensure nobody has to guess.
Management should report both dollars and rates
A percentage can hide scale.
A dollar number can hide efficiency.
Show both.
For example:
GPV
$120.0M
+20% YoY
Net Payment Contribution
$104.3M
+15.9% YoY
Payment contribution ratio
86.9%
down 3.1 percentage points
Management now knows three separate things:
activity grew strongly;
retained payment value also grew;
payment economics deteriorated per dollar processed.
That creates an investigation.
Then explain the deterioration
The waterfall should show contribution to the change.
For the hypothetical example:
Leakage
Year 1
Year 2
Change
Refunds
$5.0M
$8.0M
+$3.0M
Fraud loss
$0.8M
$1.4M
+$0.6M
Net chargeback loss
$0.7M
$1.0M
+$0.3M
Direct payment cost
$2.8M
$3.8M
+$1.0M
Payment operations
$0.7M
$1.5M
+$0.8M
Now finance can ask:
Was refund growth caused by product mix?
Did fraud worsen in a particular market?
Did payment cost rise because of transaction geography or provider pricing?
Did operations scale inefficiently?
The waterfall does not answer all of those questions.
It tells management which questions deserve a dedicated analysis.
Segment before taking action
A global contribution ratio can hide very different economics underneath.
Break the model down where useful by:
market;
currency;
payment method;
PSP/acquirer;
customer cohort;
product;
card type;
order value.
But preserve identical definitions.
If Market X calculates fraud loss as a percentage of approved value while Market Y uses settled value, the comparison is invalid.
Likewise, compare comparable time periods and payment populations.
The brief explicitly requires cohort controls such as geography, payment method, transaction value, and customer segment when evaluating payment performance.
Payment reporting should answer four questions
A mature management report should let a CFO answer:
How much payment demand entered the funnel?
Attempted payment value.
How much became successful paid activity?
Completed paid value / defined GPV.
How much remained after payment-specific leakage?
Net Payment Contribution.
Why did the gap change?
Refunds, fraud, chargebacks, direct fees, operations, and relevant upstream payment performance.
Without all four, teams can optimize the metric they happen to own rather than the economics the merchant actually cares about.
The number to put next to GPV
GPV does not need to disappear from the dashboard.
It needs context.
Put beside it:
Net Payment Contribution
and underneath:
Net Payment Contribution ÷ Completed Paid Value
Then expose the waterfall that connects them.
GPV tells management how much payment activity the business generated.
The waterfall tells management how much of that activity survived the payment system's economically relevant leakage.
The useful question at quarter-end is therefore not:
“Did payment volume grow?”
It is:
“For every dollar that successfully entered the payment system, how much did we retain—and why did that percentage change?”
That is the point at which payment reporting stops being a traffic counter and becomes an economic management system.
Gross Payment Volume vs Net Payment Revenue — Editorial Delivery Pack
Concise interpretation of the editorial brief
This article owns the bridge from gross payment activity to retained merchant economic value. It should resolve a reporting problem: finance, payments, and management teams often use GPV, approved volume, settled value, revenue, and “net revenue” as though they describe the same number, even though each can represent a different stage of the payment lifecycle.
The article’s distinctive asset is a Gross-to-Net Payment Waterfall. It begins with payment activity, follows value through approval and completion, then removes refunds, fraud loss, chargeback loss, direct payment cost, and—where explicitly included—attributable payment operations cost to reach a deliberately defined management metric: Net Payment Contribution.
The article should not imply that this management metric is GAAP or IFRS “revenue.” IFRS 15 bases revenue recognition on contracts, performance obligations, transaction price, and when those obligations are satisfied; U.S. ASC 606 likewise governs revenue recognition and gross-versus-net presentation rather than treating raw payment volume as revenue.
Merchant economics problem
A payment dashboard can show:
GPV: +20%
while hiding:
a higher refund rate;
more unrecovered fraud;
larger chargeback losses;
higher payment-processing expense;
more reconciliation and payment-operations work.
Payment activity grew.
Merchant economics may have improved less—or deteriorated.
Primary denominator
The main denominator should be:
completed paid value
for the article's contribution-rate calculations.
Other denominators may appear, but they must be labeled:
attempted value;
approved value;
completed paid value;
settled value;
transaction count.
The brief explicitly requires denominator discipline because payment cost, fraud rate, approval rate, and contribution ratios become meaningless when the denominator changes silently.
Cost scope
Core waterfall:
direct payment-processing cost;
explicitly included ancillary payment cost;
refunds;
unrecovered fraud loss;
net chargeback/dispute loss.
Advanced version:
directly attributable payment operations.
Exclude unless deliberately modeled:
general corporate overhead;
product COGS;
fulfillment;
taxes;
general sales and marketing;
broad technology overhead.
Performance scope
This article should show the transition from:
attempt
→ approval
→ completed paid value
without turning into the dedicated declines or conversion article.
Revenue leakage mechanism
The owned leakage is post-activity erosion:
refunds;
fraud;
disputes;
direct payment fees;
attributable operating expense.
Decline-related lost opportunity can be shown before GPV but should be linked to the dedicated declines article rather than modeled deeply here.
Unique evidence anchor
GPV moves:
$100 million → $120 million
The board slide looks good.
But the economic question is:
How much of each dollar of completed payment value is still retained after payment-specific leakage?
Editorial position
Every material GPV or payment-volume KPI should have a corresponding gross-to-net payment economics view.
Common assumption challenged
“Growing payment volume means the payment function is creating more value.”
Merchant decision
Determine whether payment growth is producing:
more retained value;
merely more processing activity; or
more activity with worsening payment-unit economics.
Selected format
Gross-to-net payment waterfall
Structural rationale
Start with the largest headline metric and progressively remove leakage.
The structure deliberately avoids another provider-comparison anecdote and stays within the brief's owned territory of payment metric translation rather than provider TCO, decline recovery, or fraud optimization.
Proposed architecture
The dashboard says +20%. The economics say something else.
GPV is activity, not accounting revenue
Attempted, approved, completed, and settled value
Define GPV before using it
Refunds remove retained value
Fraud and chargebacks require separate treatment
Payment fees turn volume into cost
Gross-to-Net Payment Waterfall
Define Net Payment Contribution
Avoid double counting
Why payout value is another different number
Report growth and retention together
The payment economics dashboard finance actually needs
Original practical asset: Gross-to-Net Payment Waterfall
Layer 1 — Funnel
Field
Definition
Value
Unique payment-intent value
Underlying customer payment demand
Authorization-attempt value
Includes retries where applicable
Approved value
Successfully authorized value
Completed paid value
Successful paid/completed population
GPV
Merchant-defined volume KPI
Layer 2 — Post-payment leakage
Line
Amount
% of completed paid value
Completed paid value
100.00%
Less: refunds
Less: unrecovered fraud loss
Less: net chargeback loss
Less: direct payment cost
Less: attributable payment operations
Net Payment Contribution
Payment contribution ratio
Layer 3 — Reconciliation controls
For each line record:
source system;
owner;
accounting/payment date basis;
currency normalization;
denominator;
exclusions;
overlap rule;
reconciliation status.
Hypothetical worked waterfall
Metric
Year 1
Year 2
Completed paid value / illustrative GPV
$100.0M
$120.0M
Refunds
($5.0M)
($8.0M)
Unrecovered fraud loss
($0.8M)
($1.4M)
Net chargeback loss
($0.7M)
($1.0M)
Direct payment cost
($2.8M)
($3.8M)
Payment operations
($0.7M)
($1.5M)
Net Payment Contribution
$90.0M
$104.3M
Contribution ratio
90.0%
86.9%
Result
GPV growth: +20.0%
Net Payment Contribution growth: approximately +15.9%
Contribution-ratio movement: approximately −3.1 percentage points
Double-counting control matrix
Event
Primary line
Do not duplicate in
Customer refund principal
Refunds
Chargeback loss
Fraud transaction recovered via chargeback classification
Chosen fraud or chargeback treatment
Both
Successful representment
Net chargeback calculation
Separate “revenue” line unless methodology requires
Network fee contained in all-in PSP price
Direct payment cost
Additional scheme fee
Refund already netted in payout
Settlement reconciliation
Second refund deduction
Chargeback labor already allocated to dispute economics
Chargeback cost
Broad operations
Temporary withheld deposit
Separate cash/liquidity view
Permanent payment loss without evidence
Measurement plan
Weekly operating view
Track:
attempted value;
approved value;
completed paid value;
refund initiation;
chargeback activity;
direct payment cost where data is sufficiently timely.
Use for anomaly detection, not necessarily final financial measurement.
Monthly finance view
Reconcile:
completed payment value;
refunds;
fraud loss;
chargebacks;
direct payment fees;
provider settlement;
bank payout;
attributable operations.
Quarterly management view
Report:
GPV / completed paid value growth.
Net Payment Contribution growth.
Payment contribution ratio.
Leakage waterfall.
Largest drivers of year-over-year change.
Material market/method/provider outliers.
Reporting controls
Every dashboard should identify:
Period basis
Transaction date, settlement date, payout date, or accounting period.
Currency basis
Original transaction currencies versus reporting-currency normalization.
GPV definition
Explicit.
Refund scope
Full and partial.
Fraud-loss methodology
Explicit.
Chargeback treatment
Gross reversals, recovery, and fee treatment.
Direct payment-cost scope
Exactly which fees are included.
Operations scope
Which teams/activities are attributed.
Net Payment Contribution
Formula visibly documented.
SEO metadata
H1: Gross Payment Volume vs Net Payment Revenue: What Merchants Actually Retain From Payments
Meta description: Learn why GPV does not equal merchant revenue and how to build a gross-to-net payment waterfall covering completed payment value, refunds, fraud, chargebacks, payment fees and attributable operating cost.
URL slug: /gross-payment-volume-vs-net-payment-revenue/
Secondary keywords:
GPV vs net revenue
gross payment volume
net payment revenue
payment volume vs revenue
merchant payment contribution
payment revenue waterfall
processed volume economics
retained payment revenue
Related entities:
gross payment volume
GPV
TPV
payment contribution
completed paid value
approval rate
settled volume
refunds
fraud
chargebacks
payment-processing fees
payment operations
IFRS 15
revenue recognition
Article excerpt:
GPV measures payment activity, not the economic value a merchant ultimately retains. A gross-to-net payment waterfall shows how completed payment value is reduced by refunds, fraud, chargebacks, payment costs and attributable payment operations.
Suggested structured data:
Article or BlogPosting.
Internal-link recommendations
How to Calculate the True Cost per Transaction
Link from direct payment cost and denominator methodology.
How Fraud Affects Net Revenue
Link where fraud loss becomes material rather than reproducing fraud-control economics.
How Chargebacks Affect Net Revenue
Link from net dispute-loss treatment.
Net Revenue Optimization
Link after the reporting framework for decisions that span approvals, cost, fraud, operations, and provider architecture.
This article should retain ownership of gross-volume-to-retained-value translation, while those adjacent pieces own the individual leakage mechanisms and optimization decisions.
Authoritative source recommendations
Merchant first-party data
Highest priority:
payment-intent data;
authorization data;
captured/completed transaction records;
refunds;
fraud reporting;
dispute/chargeback records;
PSP/acquirer statements;
finance reconciliation;
payment-operations cost records.
The brief explicitly prioritizes merchant transaction and finance data above general external benchmarks for this cluster.
IFRS Foundation — IFRS 15
Use for the important boundary that accounting revenue is governed by accounting principles and contract/performance-obligation analysis rather than payment-volume terminology.
SEC / ASC 606 context
Useful if the publication needs a U.S.-GAAP reference. SEC Staff Accounting Bulletin 116 notes that ASC Topic 606 governs revenue recognition from contracts with customers and includes gross-versus-net presentation considerations.
Supporting visual
Gross-to-Net Payment Waterfall
Top bar
Attempted customer value
Narrow to:
Approved value
Narrow to:
Completed paid value / defined GPV
Then waterfall deductions:
Refunds
↓
Fraud loss
↓
Net chargeback loss
↓
Direct payment cost
↓
Attributable payment operations
↓
Net Payment Contribution
Side annotation
Not accounting revenue
Management payment-economics metric; define scope and obtain accounting review before using financial-reporting terminology.
Comparison panel
Show two periods:
GPV
$100M → $120M
+20%
Net Payment Contribution
$90.0M → $104.3M
+15.9%
Contribution ratio
90.0% → 86.9%
Image alt text
“Gross-to-Net Payment Waterfall showing attempted payment value, approved value, completed paid value, refunds, fraud loss, chargeback loss, payment fees and payment operations leading to Net Payment Contribution.”
Proposed author and reviewers
Proposed author:
Payments analytics or merchant-economics specialist.
Recommended reviewers:
Merchant finance lead.
Payments analytics lead.
Accounting reviewer for revenue terminology.
Payments operations reviewer for attributable-cost treatment.
Do not name individuals until participation is confirmed.
Recommended first-hand contribution
GPV growth;
refund changes;
fraud/dispute losses;
direct payment fees
translated into a different growth rate for retained payment contribution.
Do not invent merchant performance data.
Cost fact-check items
Before publication confirm:
GPV definition.
Direct payment-cost scope.
Percentage versus fixed charges.
Whether FX is included.
Whether settlement/payout costs are included.
Whether refund fees are included.
Whether dispute fees are included.
Operations allocation method.
Currency normalization.
Period.
Conversion and approval fact-check items
If the article includes upstream funnel numbers, verify:
authorization attempt definition;
approval definition;
payment-completion definition;
retries;
duplicate attempts;
order cohort;
payment-method switching.
Do not describe:
attempted − completed value
as lost revenue.
The brief explicitly requires incrementality and recoverability before converting failed-payment volume into economic opportunity.
Decline fact-check items
Where declines are mentioned:
distinguish issuer decline;
fraud-rule decline;
technical failure;
recoverable decline;
false decline;
eventually recovered payment.
Do not subtract gross declined value from payment contribution.
Fraud fact-check items
Verify:
fraud definition;
count or value denominator;
actual merchant loss;
recoveries;
chargeback overlap;
product/service loss if included;
fraud-tool expense if included.
Do not compare fraud rates using inconsistent denominators.
Chargeback fact-check items
Verify:
reversed principal;
dispute fee;
representment recovery;
fraud overlap;
refunded-before-chargeback cases;
goods/service cost if included;
operational labor if included.
Use net chargeback loss only after defining recoveries and exclusions.
Operations/TCO assumptions
For this article, operations should remain a narrow optional extension.
Acceptable examples:
payment reconciliation;
settlement exception work;
provider management;
payment-specific dispute operations;
payment-specific support;
payment reporting.
Avoid allocating broad:
executive expense;
company finance;
infrastructure;
engineering;
customer support
unless a defensible activity-based methodology attributes the work to payments.
Provider integration and ownership costs belong primarily in the dedicated PSP TCO article.
Merchant margin assumptions
Net Payment Contribution is not product contribution margin.
If the article discusses the economic value of:
recovered declines;
additional payment methods;
higher approval;
incremental orders,
use contribution profit where data exists rather than equating a $100 recovered order with $100 of merchant benefit.
That calculation belongs mostly in adjacent articles, so keep it high-level here.
Experiment and incrementality fact-check items
If a future version claims an optimization improved Net Payment Contribution:
verify:
control/comparison cohort;
geography;
payment method;
transaction value;
customer mix;
time period;
fraud;
refunds;
disputes;
payment cost;
completed-order effect.
Ask:
Would the order have happened anyway?
Do not treat rerouted or shifted existing volume as incremental revenue.
Amber-flag claims
Require verification before publishing any claim that:
GPV has one universal definition;
GPV equals accounting revenue;
settled volume equals GPV;
bank payout equals net revenue;
every decline is lost revenue;
every fraud event becomes a chargeback;
every chargeback is fraud;
refunds and chargebacks can always be summed without overlap;
a payment-cost rate represents the total economic cost of payments;
higher GPV automatically creates more profit;
higher Net Payment Contribution automatically means better company profitability;
Second, its current API documentation describes a Reporting API that allows merchants to pull Merchant Account reports when the capability is activated.
Which reporting fields correspond to completed paid value.
How refunds are represented.
How chargebacks are represented.
How fees/commissions are represented.
Fraud-loss reporting availability.
Approval/decline reporting.
Currency normalization.
Net settlement calculation by product.
Deposit/reserve treatment.
Pending versus collected funds.
Merchant-level reporting exports.
Current APIs/reporting tooling.
Any approved Net Payment Contribution framework.
Approved merchant outcomes.
Do not infer a full gross-to-net economics dashboard from the existence of the Reporting API alone.
Cluster sameness-audit fields
Title:
Gross Payment Volume vs Net Payment Revenue: What Merchants Actually Retain From Payments
First two sentences:
“The board slide contains a green arrow: GPV +20%. Last year: $100 million. This year: $120 million.”
Opening device:
Management-dashboard contradiction.
Merchant economics problem:
Growth in payment activity can outrun growth in retained payment value.
Primary denominator:
Completed paid value.
Direct cost variable:
Defined direct payment cost.
Performance variable:
Attempt → approval → completion, at boundary level.
Revenue leakage variables:
Refunds, fraud, chargebacks, direct payment costs, optional attributable operations.
Primary format:
Gross-to-net payment waterfall.
Unique evidence anchor:
$100M → $120M GPV while payment contribution grows more slowly.
Editorial position:
Pair volume KPIs with a defined payment-contribution waterfall.
Common assumption challenged:
“Growing payment volume means the payment function is creating more value.”
Merchant decision:
Determine whether growth is improving absolute retained value and payment-unit economics.
Original framework:
Gross-to-Net Payment Waterfall.
Primary metrics:
completed paid value / defined GPV;
Net Payment Contribution;
payment contribution ratio.
Conclusion device:
“The number to put next to GPV” rather than another generic Final Recommendation or FAQ.
CTA direction:
Define the merchant's GPV denominator, build the waterfall from actual finance/payment data, and explain every material change in payment contribution ratio.
Publication status
Article structure: Ready.
Unique opening: Ready; deliberately avoids provider/customer A-versus-B construction in line with the new editorial instruction.
GPV definition discipline: Ready.
Gross-to-net framework: Ready.
Refund/fraud/chargeback separation: Ready.
Double-counting controls: Ready.
Management-versus-accounting terminology: Grounded in current IFRS guidance and U.S. ASC 606 context.
Named author and reviewers: Require assignment.
Real merchant waterfall: Recommended before publication if approved first-party data is available.
Need help narrowing down payment options?
Answer a few questions about your business and compare the capabilities that matter to you.
Explore matching options ↗