Comparing PSP Pricing
Three pricing proposals reach the procurement team on the same afternoon. One says: 1.90% Another says: Interchange++ + 0.25% The third says: 1.40% + $0.18 per transaction The spreadsheet owner highlights 1.40%. It is the smallest percentage. It may not be the cheapest proposal.
Comparing PSP Pricing: How to Normalize Provider Quotes Before Choosing a Deal
Three pricing proposals reach the procurement team on the same afternoon.
One says:
1.90%
Another says:
Interchange++ + 0.25%
The third says:
1.40% + $0.18 per transaction
The spreadsheet owner highlights 1.40%.
It is the smallest percentage.
It may not be the cheapest proposal.
In fact, asking which percentage is lowest is the wrong first question, because the three quotes do not describe cost in the same way. One may bundle underlying card costs. Another passes them through. A third can look inexpensive on percentage pricing while collecting far more through a fixed transaction charge. International fees, FX, payment-method pricing, platform fees, volume tiers and minimum commitments can change the ranking again.
The only defensible comparison is to translate every proposal into the same merchant portfolio:
the same transactions, the same markets, the same payment methods, the same currencies and the same volume assumptions.
Then calculate what the merchant would actually pay.
That is the central rule for comparing PSP pricing:
Do not compare provider percentages. Compare modeled annual cost on an identical merchant transaction portfolio.
The short version: how to compare PSP pricing
A reliable PSP pricing comparison has seven steps:
Freeze one merchant transaction dataset.
Translate every pricing model into explicit cost components.
Apply each proposal to exactly the same transaction mix.
Add fixed, international, FX, method-specific and ancillary costs that belong in scope.
Apply volume tiers, commitments and minimums exactly as contracted.
Run current, growth and downside scenarios.
Compare total annual cost first; derive effective rate and cost per transaction second.
Only after commercial pricing is normalized should the merchant widen the decision to:
approval performance;
payment coverage;
operations;
implementation;
resilience;
full provider TCO.
Those are important.
They answer a different question.
This article owns the price comparison.
Why PSP quotes resist direct comparison
Payment providers can price the same merchant using materially different commercial structures.
A proposal may include:
blended percentage pricing;
interchange-plus or interchange++ pricing;
fixed transaction fees;
payment-method-specific schedules;
platform or account fees;
cross-border additions;
FX charges;
refund or dispute charges;
minimum commitments;
volume tiers.
Even the phrase:
“processing rate”
may refer to a different bundle of costs in different proposals.
That is why the brief's primary evidence anchor is so important: two PSP offers can use different pricing structures and assumptions, making the apparently lower headline rate impossible to compare directly.
First separate underlying payment cost from provider pricing
Before normalizing a proposal, identify what the quoted price includes.
For card payments, some underlying economics may sit outside the provider's own commercial markup.
Visa currently describes interchange reimbursement fees as transfer fees between acquiring and issuing banks and notes that merchants instead negotiate a merchant discount with their financial institution. Mastercard similarly states that interchange is one component of the merchant discount rate and that Mastercard does not determine the commercial pricing agreement between acquirer and merchant.
That distinction matters when comparing:
Blended quote
1.90%
against:
Interchange-plus quote
underlying cost + 0.25%
The 0.25% is not necessarily comparable with 1.90%.
The merchant must first model the underlying costs that the interchange-plus proposal passes through.
Do not compare PSP markup with total effective processing cost
This is one of the easiest procurement mistakes to make.
Suppose a proposal reads:
Interchange++ + 25 bps
and another reads:
1.85% all-in.
It is incorrect to conclude:
25 bps is cheaper than 1.85%.
The first figure represents only one layer of the price.
The second may contain several layers.
The normalized comparison must estimate:
underlying/pass-through cost
provider/acquirer markup
fixed transaction charges
other relevant commercial charges
for both.
Only then do you have comparable totals.
Start with the merchant portfolio—not the proposal
The comparison model should begin with merchant data.
For the measurement period record:
processed payment volume;
transaction count;
average transaction value;
country mix;
issuer/card mix where relevant;
domestic versus international mix;
payment-method mix;
currency mix;
refund/dispute mix where priced separately;
current provider share.
This portfolio becomes the common denominator for every proposal.
The provider does not get to choose a different set of assumptions merely because those assumptions make its quote look better.
Freeze the same transaction file for every provider
The strongest comparison uses a transaction-level or sufficiently granular aggregated dataset.
For each segment, preserve fields such as:
Field
Why it matters
Transaction value
Percentage-price impact
Transaction count
Fixed-fee burden
Country / acquiring market
Geographic pricing
Issuer geography
Cross-border classification where applicable
Card/payment type
Underlying cost
Payment method
Method-specific pricing
Currency
FX or settlement implications
Provider route
Existing internal benchmark
Refund/dispute events
Conditional charges where included
Then run each proposal against that same file.
This removes one of the biggest sources of misleading PSP comparisons: different providers quoting against different portfolio assumptions.
Normalize pricing model first
Create the same cost buckets for every proposal.
Underlying or pass-through payment cost
Where the commercial model passes through underlying card or method cost, model it using the merchant's actual or appropriately estimated transaction mix.
Do not invent a universal interchange percentage.
Mastercard's current documentation itself illustrates why: interchange qualification varies with factors including product type, merchant category, authorization-to-clearing timing, transaction data and volume.
PSP or acquiring markup
Record the provider-controlled commercial component separately where the quote allows it.
Examples might include:
percentage markup;
basis-point markup;
acquiring margin.
Do not assume all provider margin is negotiable or observable.
Use the actual proposal.
Fixed transaction cost
For example:
$0.05 per transaction
or:
€0.10 per successful payment.
Fixed cost can materially change proposal economics when ticket size is low.
Payment-method pricing
Cards, bank payments, wallets, cash methods and other payment methods can have different commercial schedules.
Apply the correct schedule to the actual method mix.
Do not average everything into one invented global rate.
Cross-border and international additions
Include only charges that genuinely apply to the modeled transaction segment.
Do not treat:
cross-border fee;
FX fee;
as synonyms.
They represent different economic mechanisms.
FX
If the proposal includes provider conversion, incorporate the applicable merchant FX cost using the methodology defined in the merchant's FX analysis.
This article does not own FX benchmarking methodology.
It imports a verified cost input.
Ancillary charges
Depending on the contract, potentially include relevant:
refund charges;
dispute charges;
payout fees;
account fees;
other recurring commercial items.
Do not expand the model into a complete ancillary-fee audit unless those costs materially change the procurement comparison.
Platform and account fees
Convert:
monthly fees;
annual account charges;
gateway fees;
into the same annual period as the rest of the model.
Volume tiers
Model the tier exactly as written.
Do not assume:
more volume automatically means the cheaper rate applies to all volume.
Tier mechanics differ.
Minimum commitments
A proposal can have the lowest variable rate and still become expensive when volume falls below its commitment.
Model the shortfall.
The PSP Pricing Comparison Model
The complete normalized structure is:
Variable cost
Underlying/payment cost
provider/acquirer percentage markup
payment-method charges
applicable international cost
FX cost included in scope
Transaction cost
fixed transaction fees
Fixed commercial cost
platform/account charges
other included fixed fees
Conditional cost
ancillary charges
minimum shortfall
=
Total Annual Provider Cost
Then derive:
Effective provider cost rate
Total annual provider cost
÷ eligible processed value
and:
Cost per transaction
Total annual provider cost
÷ modeled transactions
This is the brief's required normalization framework.
A normalized example
Consider a hypothetical merchant with:
$480 million annual processing volume
across:
12 million transactions.
Average transaction value:
$40.
Quote 1 — Flat commercial model
1.90% + $0.02 per transaction
Percentage cost:
$480m × 1.90% = $9.12m
Fixed transaction cost:
12m × $0.02 = $240,000
Total:
$9.36 million
Effective modeled rate:
1.95%
Cost per transaction:
$0.78
Quote 2 — Interchange-plus structure
Assume the merchant's actual modeled underlying cost for this illustrative portfolio is:
1.34%
Commercial terms:
underlying cost + 0.25% + $0.04 per transaction
plus:
$120,000 annual platform charge
Underlying cost:
$480m × 1.34% = $6.432m
Provider markup:
$480m × 0.25% = $1.200m
Fixed transaction cost:
12m × $0.04 = $480,000
Platform:
$120,000
Total:
$8.232 million
Effective modeled rate:
1.715%
Cost per transaction:
$0.686
Quote 3 — Low percentage, high fixed fee
1.40% + $0.18 per transaction
plus:
$150,000 annual platform charge
Percentage cost:
$480m × 1.40% = $6.72m
Fixed transaction cost:
12m × $0.18 = $2.16m
Platform:
$150,000
Total:
$9.03 million
Effective modeled rate:
1.881%
Cost per transaction:
$0.753
The 1.40% quote was not the cheapest
Normalized result:
Quote
Headline
Annual modeled cost
Effective rate
Cost / transaction
Flat model
1.90% + $0.02
$9.36m
1.950%
$0.780
Interchange-plus
1.34% underlying + 0.25% + $0.04 + platform
$8.232m
1.715%
$0.686
Low % + fixed fee
1.40% + $0.18 + platform
$9.03m
1.881%
$0.753
The smallest advertised percentage ranks second.
The 25-basis-point markup proposal ranks first only because the model also included the underlying cost and fixed charges required to make the comparison fair.
That is exactly what quote normalization is supposed to reveal.
Average ticket changes the ranking
Fixed fees deserve particular attention because their effective percentage impact depends on transaction value.
A:
$0.20
fixed fee is:
2% of a $10 transaction
before any percentage fee is added.
The same $0.20 is:
0.2% of a $100 transaction.
Therefore two merchants with the same annual volume can experience very different proposal economics if one processes:
many low-value transactions;
and the other:
fewer high-value transactions.
Always model:
volume + transaction count.
Not volume alone.
Do not normalize using one average ticket if the portfolio is highly skewed
A merchant with:
$5 microtransactions;
$30 consumer orders;
$500 enterprise purchases;
can produce a misleading answer if all transactions are replaced with one average ticket.
Where fixed fees materially affect economics, model meaningful ticket-size segments separately.
For example:
Segment
Transactions
Volume
Average ticket
Micro
Standard
High value
Then apply each quote to every segment.
Payment-method mix can change the comparison
A merchant might receive one attractive card quote but have 35% of volume coming through bank transfers, wallets, or other local payment methods.
If the proposals price those methods differently, comparing the card rate alone answers the wrong question.
Model:
expected provider cost across the merchant's actual payment-method portfolio.
International mix can change the winner
A provider can look inexpensive on domestic traffic and expensive once the merchant introduces:
international cards;
cross-border additions;
foreign currencies;
international payment methods.
Therefore model geography explicitly.
A quote comparison that assumes:
90% domestic traffic
is not appropriate for a merchant whose growth case may become:
55% domestic / 45% international.
That is why the proposal needs more than one scenario.
Public price and negotiated quote are not equivalent evidence
Do not compare:
one provider's public small-business price
against:
another provider's negotiated enterprise proposal
and call the difference provider competitiveness.
Every price input should be tagged as:
public;
quoted;
negotiated;
historical;
hypothetical.
The brief makes this distinction mandatory.
For procurement, the strongest evidence is the commercial proposal actually available to the merchant.
Volume tiers need their own model
“Volume discount” is not one pricing mechanic.
A contract can use:
Threshold pricing
Rate changes after a defined threshold.
Marginal tiering
Only volume above a threshold receives the lower rate.
Blended tiering
The achieved total-volume band determines an applicable rate.
Contractual step-down
Pricing changes at negotiated volume milestones.
Do not model a tier until procurement understands exactly which mechanic applies.
Why this matters
Suppose the quote says:
0.25% above $50 million monthly volume.
That wording alone may be insufficient.
Does 0.25% apply to:
all $60 million
once the threshold is reached?
Or only:
the $10 million above $50 million?
Those produce different economics.
Ask before modeling.
Minimum commitments can reverse the result
Now add a hypothetical minimum to the interchange-plus quote:
$7 million minimum annual provider spend.
Suppose a downside case produces:
$300 million volume
across:
10 million transactions.
Without the minimum, the modeled commercial cost might be approximately:
$5.29 million
under the illustrative assumptions.
But the contract requires:
$7 million.
Effective annual cost becomes:
$7 million
and the minimum shortfall is:
$1.71 million.
Effective cost rate on $300 million:
2.33%.
The proposal that was cheapest in the current case can become most expensive in the downside case.
That is why minimum exposure belongs in a normalized quote comparison.
Never assess a commitment only against the optimistic forecast
If the commercial team forecasts:
50% growth,
procurement still needs to model:
current volume;
forecast growth;
downside volume.
The question is not:
“Can we hit the minimum if everything goes to plan?”
It is:
“What happens to effective pricing if volume, market mix, ticket size or provider share develops differently?”
Run three scenarios
The brief requires at least:
Current case
Use the merchant's most recent representative portfolio.
This answers:
What would each quote cost if the business looked like it does now?
Growth case
Model the most defensible expected future mix.
Consider changes in:
volume;
transactions;
ticket size;
countries;
payment methods;
international share;
card mix.
This answers:
Which commercial structure scales best with our actual growth plan?
Downside case
Stress assumptions such as:
lower volume;
lower ticket;
higher international mix;
more expensive card mix;
missed minimum;
lower provider share.
This answers:
Which quote becomes dangerous if the forecast is wrong?
Scenario rankings can legitimately differ
The preferred quote does not have to remain the same in every scenario.
That is useful information.
For example:
Current case
Interchange-plus may be lowest.
Growth case
Interchange-plus may become even more attractive as fixed costs dilute.
Downside case
A flat proposal without a large minimum might become cheaper.
The procurement question then becomes:
How much pricing volatility is the merchant willing to accept?
Add pricing volatility as an output
A proposal with the lowest expected annual cost can still expose the merchant to more uncertainty.
Possible sources include:
pass-through underlying-cost variation;
mix sensitivity;
FX;
international share;
minimums;
volume tiers.
Track:
Scenario cost variance
highest modeled annual cost − lowest modeled annual cost
and preferably compare the reasons for that variance.
This is not a substitute for total cost.
It is an additional procurement signal.
Compare total annual cost before effective rate
Effective rate is useful.
But total annual dollar cost should usually lead the commercial comparison.
Why?
Because procurement ultimately needs to know:
how many dollars does each proposal cost under the modeled business?
Only then derive:
effective rate
for comparability and diagnosis.
A 15-basis-point difference sounds abstract.
A:
$720,000 annual difference
is easier to evaluate against:
negotiation effort;
migration expense;
operating complexity.
Calculate effective rate consistently
Use:
Effective pricing rate
Total included annual provider cost
÷ eligible processed value
State what cost is included.
If the model excludes:
FX;
disputes;
payout fees;
say so.
Do not compare:
Provider 1 effective rate including all fixed costs
with:
Provider 2 transaction percentage excluding platform cost.
Calculate cost per transaction too
Use:
Cost per transaction
Total included provider cost
÷ modeled transaction count
This becomes particularly useful when:
providers have different fixed fees;
merchant ticket sizes are low;
transaction counts grow faster than volume.
A percentage-only model hides that sensitivity.
Track provider markup separately where possible
Even after total-cost normalization, procurement should preserve:
Provider-controlled markup
as a separate field where the commercial structure exposes it.
Why?
Because it helps distinguish:
quote comparison
from:
future negotiation leverage.
If underlying cost changes while markup remains the same, the reason total expense moved becomes visible.
But do not force markup extraction where the quote does not support it
A blended price may not provide enough information to cleanly separate:
underlying cost;
provider margin.
Do not invent the split.
Instead classify:
provider-controlled markup: not observable from proposal
and compare the all-in modeled cost.
That is better than false precision.
International and FX costs need clean boundaries
A cross-border addition can exist without merchant-side currency conversion.
Merchant-side FX can occur without the same cross-border fee.
Therefore separate:
Geographic processing premium
from:
Currency-conversion cost
The Cross-Border Costs and Foreign Exchange clusters own those mechanics in depth.
This article should import their verified commercial inputs into the quote model.
Ancillary costs matter only when they can change the decision
Do not overload procurement with fifty fee categories merely because they exist.
Prioritize:
recurring material charges;
likely event-based charges;
costs that differ significantly across proposals.
A rarely triggered minor fee should not dominate a $10 million annual processing decision.
Materiality still applies.
Proposal terms and quote comparison are different tasks
A proposal-reading article should answer:
What does this pricing term mean?
This article answers:
What does this term cost our business relative to the alternatives?
That distinction prevents cannibalization with How to Read a PSP Pricing Proposal.
Benchmarking and quote comparison are also different
A payment-cost benchmark asks:
Is our current or proposed pricing high or low relative to an appropriate comparison?
A quote comparison asks:
Which of the commercial offers currently available to us costs less under the same portfolio?
The merchant can compare three quotes without knowing whether any of them are objectively attractive.
Conversely, a benchmark can tell the merchant current pricing looks expensive without providing an executable alternative.
Link the two analyses.
Do not merge them.
What constitutes a strong benchmark?
The brief's benchmark-quality hierarchy is useful:
Strong
Same merchant.
Comparable transactions.
Alternative provider or route.
Good
Comparable merchant segment with properly normalized mix.
Directional
Public or market information with meaningful differences.
Weak
Unverified anecdote or unrelated merchant quote.
Weak evidence can start a procurement question.
It should not be presented as proof that the merchant is overpaying.
A quote comparison is not full provider TCO
Suppose one proposal costs:
$600,000 less per year
commercially.
That does not yet establish:
the provider is economically $600,000 better.
A full provider decision can include:
implementation;
migration;
engineering;
reconciliation;
support;
reliability;
payment performance;
switching;
exit.
Those belong in Total Cost of Ownership for a Payment Provider and broader net-payment-economics analysis.
This article should hand procurement a clean commercial cost comparison first.
A quote comparison is not a performance ranking either
The lowest commercial price can still become a poor overall economic choice if:
approval is weaker;
customer coverage is poorer;
operational burden is materially higher.
But do not insert unverified performance assumptions into the quote model just to make it look sophisticated.
Use a two-stage decision.
Stage 1
Normalize commercial price.
Stage 2
Apply payment-performance and TCO guardrails using defensible evidence.
That preserves analytical clarity.
Performance should still be visible as a guardrail
For every proposal, keep adjacent fields for:
authorization approval;
completed payment;
completed order;
reliability where measured.
If performance is not yet known:
mark it unknown.
Do not assume:
same price model = same performance
or:
higher price = higher performance.
Ask how much performance loss would erase the saving
This creates a useful bridge to the True Cost and Net Revenue cluster.
Suppose a new provider saves:
$500,000 annually
in normalized commercial cost.
If merchant contribution per incremental completed order is:
$25,
then:
$500,000 ÷ $25 = 20,000 completed orders.
A performance deterioration that causes more than 20,000 otherwise-profitable orders to disappear could erase the gross commercial saving before other effects.
The values are illustrative.
This article does not need to determine whether performance will change.
It should tell procurement how much deterioration the commercial saving can tolerate.
Price comparison before negotiation
Once the quotes are normalized, procurement can make a much more specific negotiation ask.
Instead of:
“Another provider quoted a lower rate.”
say:
“Under our trailing transaction mix, your proposal models $780,000 above the best comparable alternative, with approximately $420,000 attributable to the percentage markup and $360,000 to the fixed transaction charge.”
That is a negotiation position.
It identifies:
the gap;
the component;
the merchant portfolio producing it.
Avoid fake precision
PSP quote models contain assumptions.
Tag them.
For example:
Verified
trailing transaction count;
trailing volume;
signed rate;
known platform fee.
Modeled
future volume;
projected country mix;
future payment-method mix.
Unknown
final acquiring configuration;
future card mix;
contingent fee.
Procurement should understand which part of the cost estimate is fact and which part is forecast.
Build a sensitivity table
For each provider, test the variables most likely to change price.
Examples:
Variable
Downside
Base
Growth
Annual payment volume
Transaction count
Average ticket
International share
Alternative-method share
Provider share
Then recalculate.
This identifies proposals whose attractiveness relies on fragile assumptions.
Model provider share explicitly
If a merchant intends to retain multiple PSPs, do not price each provider as though it will receive 100% of company volume.
Model its actual expected share.
This matters because provider share can affect:
tier qualification;
minimum commitments;
negotiating economics.
The merchant may discover that a quote is excellent at:
80% traffic share
but unattractive at:
20%.
Multi-PSP structure can change quote economics
This article does not own multi-PSP competition strategy.
But procurement cannot ignore its effect on pricing.
Splitting volume can:
miss a tier;
trigger several minimums;
reduce concentration leverage.
Conversely, a real alternative can strengthen future commercial leverage.
The dedicated How Multi-PSP Competition Affects Pricing article should own that tradeoff.
Here, just model the provider share correctly.
The PSP Pricing Comparison Model: working sheet
For each proposal, populate:
Cost field
Quote 1
Quote 2
Quote 3
Pricing model
Underlying/pass-through cost
PSP/acquirer markup
Percentage fee
Fixed transaction fee
Payment-method fees
Cross-border additions
FX included
Ancillary cost
Platform/account fee
Tier mechanics
Minimum commitment
Expected provider share
Then calculate:
Output
Quote 1
Quote 2
Quote 3
Current annual cost
Current effective rate
Current cost/transaction
Growth annual cost
Growth effective rate
Downside annual cost
Minimum shortfall
Scenario variance
That is the decision asset—not the first page of the provider proposal.
Add a Pricing Confidence column
Not every modeled number is equally trustworthy.
For each material input classify:
High confidence
Signed quote + actual merchant data.
Medium confidence
Signed quote + modeled future mix.
Low confidence
Incomplete commercial detail or directional assumption.
If the lowest-cost proposal depends heavily on low-confidence assumptions, procurement has identified its next diligence task.
What procurement should request before declaring a winner
For each finalist, obtain enough information to resolve:
exact pricing model;
what is included;
what is passed through;
fixed transaction charge;
method-specific pricing;
international additions;
FX treatment;
platform/account charges;
relevant ancillary charges;
tier mechanics;
commitment mechanics;
pricing effective date;
contract term;
expected provider share;
treatment when mix changes.
If a provider cannot yet quote a variable because the acquiring or market setup is not final, label it:
TBD
rather than inserting an industry assumption.
Compare current economics with the proposals
Do not compare only:
new offer versus new offer.
Include:
Current provider economics
as a fourth column.
Then procurement knows:
whether switching saves anything at all;
how much negotiating headroom exists;
whether the incumbent can match the alternative.
A competitive process where every new quote is more expensive than current pricing can still be useful information.
Calculate gross commercial savings
For each alternative:
Gross annual pricing saving
Current annual provider cost
− proposed annual provider cost
Use the same merchant portfolio and period.
If the proposal is more expensive:
report a negative saving.
Do not hide it.
Keep gross commercial saving separate from net economic benefit
Gross pricing saving is the output owned here.
A wider provider-selection process must then consider:
implementation;
migration;
operating cost;
performance;
other TCO effects.
So:
Commercial comparison
current modeled commercial cost
− proposed modeled commercial cost
is not automatically:
Merchant net benefit
The brief explicitly requires gross and net savings to remain distinct.
What PSP price comparison cannot tell you
A normalized cost model can tell procurement:
which quote costs least under the modeled mix;
which price is most sensitive to volume;
which minimum is risky;
how fixed fees affect ticket economics;
how rankings change by scenario.
It cannot prove:
which provider will approve more transactions;
which has better reliability;
which integration is cheaper;
which support organization is stronger;
which fraud stack produces better economics;
which provider creates the highest net contribution.
Those require other evidence.
Commercial normalization is necessary.
It is not sufficient for final provider selection.
I’m treating the upload as Article 5 of the Pricing Optimization cluster: Comparing PSP Pricing under Payments Cost Too Much. The finished asset below stays tightly within the brief’s ownership boundary: commercial quote normalization for a live procurement decision, not proposal-reading fundamentals, full PSP TCO, or provider-performance selection.
global card payment processing;
more than 150 local payment methods;
a unified payment gateway;
risk and operations services;
recurring billing and subscription capabilities.
Its current homepage also describes local acquiring in selected markets and transaction reporting capabilities.
Those capabilities can be relevant to constructing:
transaction mix;
method mix;
market mix;
current transaction evidence.
Those must be taken from current applicable commercial terms.
A defensible positioning paragraph is:
Suggested CTA
Proposal-comparison scenarios
Scenario 1: The smallest percentage loses
A merchant with millions of low-ticket transactions receives a:
low percentage + high fixed fee
proposal.
Another provider quotes a higher percentage but negligible fixed cost.
After applying transaction count:
the “lower-rate” quote costs more annually.
Procurement lesson
Model:
volume and count, not percentage alone.
Scenario 2: Interchange-plus wins today but loses in the downside case
The merchant's base portfolio produces attractive interchange-plus economics.
The proposal also carries a substantial annual commitment.
Growth occurs more slowly than expected.
The minimum activates.
Procurement lesson
A quote can be inexpensive under expected volume and expensive under realized volume.
Scenario 3: The cheapest card quote is not the cheapest merchant quote
One provider has attractive card pricing.
The merchant also needs significant local-method coverage.
Those methods have a different fee schedule.
Once the real payment-method mix is modeled, another provider has lower total commercial cost.
Procurement lesson
Compare the merchant portfolio—not one payment rail.
Scenario 4: The incumbent is still cheaper
Procurement launches an RFP expecting competitive savings.
Every normalized alternative costs more on the current portfolio.
Procurement lesson
A competitive process does not have to produce a provider switch to be useful.
It may validate the incumbent's commercial position or expose only specific components worth renegotiating.
Scenario 5: A quote wins on price but requires a separate economic review
One provider models:
$800,000 cheaper annually.
Its performance on the relevant merchant cohort has not been tested.
Procurement lesson
The commercial model identifies a candidate.
It does not replace:
performance diligence;
TCO;
migration economics.
PSP pricing comparison checklist
Before choosing a commercial winner:
Portfolio normalization
Same merchant period used
Same payment volume
Same transaction count
Same country mix
Same card/issuer mix where material
Same payment-method mix
Same international mix
Same currencies
Same expected provider share
Pricing structure
Pricing model identified
Underlying costs identified
Provider markup identified where observable
Percentage charges included
Fixed transaction fees included
Method-specific fees included
Platform/account fees included
Cross-border costs included where applicable
FX included where applicable
Material ancillary charges included
Volume mechanics
Tier definition verified
Marginal versus blended tier confirmed
Minimum commitment included
Provider-share commitment included
Growth forecast labeled as forecast
Downside case run
Outputs
Total annual provider cost
Effective rate
Cost per transaction
Provider markup where observable
Minimum exposure
Scenario variance
Evidence quality
Public prices labeled public
Negotiated quotes labeled negotiated
Current effective date confirmed
Missing pricing terms marked unknown
No unrelated benchmark inserted as fact
Decision boundary
Commercial price winner identified
Performance evidence reviewed separately
Provider TCO reviewed separately
Switching cost reviewed separately
Net economic decision not inferred from quote alone
SEO package
Comparing PSP Pricing: How to Normalize Provider Quotes
Alternative SEO title:
How to Compare PSP Pricing and Payment Processor Fees
H1:
Comparing PSP Pricing: How to Normalize Provider Quotes Before Choosing a Deal
Meta description:
Learn how to compare PSP pricing by normalizing percentage rates, interchange-plus quotes, fixed fees, payment-method costs, FX, tiers and minimums into the same merchant-specific annual cost model.
URL slug:
/comparing-psp-pricing
comparing PSP pricing
Secondary keywords:
compare PSP pricing
payment provider pricing comparison
compare payment processor fees
PSP quote comparison
payment processing pricing comparison
payment provider rates
compare merchant processing pricing
PSP pricing model comparison
payment processor quote comparison
interchange plus vs flat rate
Related entities:
payment service provider
PSP
payment processor
interchange
interchange plus
interchange++
merchant discount rate
acquirer
payment markup
fixed transaction fee
volume tier
minimum commitment
cross-border fee
FX fee
payment method pricing
effective processing rate
payment procurement
Article excerpt:
The PSP with the smallest headline percentage is not necessarily the cheapest. Merchants should normalize every provider proposal against the same transaction volume, count, market and payment-method mix, then compare annual cost, effective rate, fixed-fee burden, tiers and minimum exposure across current, growth and downside cases.
Suggested structured data:
Article + BreadcrumbList
The proposal-comparison scenarios and procurement checklist are stronger closing assets than a generic FAQ.
Recommended internal links
How to Read a PSP Pricing Proposal
Anchor:
understand what each PSP pricing term includes
Use early, before normalization.
Payment Cost Benchmarking
Anchor:
build a comparable payment-cost benchmark
Use in the benchmark-quality section.
Why the Cheapest PSP May Cost More
Anchor:
why the lowest commercial price may not produce the best merchant economics
Use from the performance/TCO boundary.
Volume-Based Payment Pricing
Anchor:
how payment volume tiers and commitments change pricing
Use in the tier section.
Also link:
How to Negotiate PSP Pricing
Anchor:
turn normalized quote differences into specific negotiation asks
When to Renegotiate Payment Fees
Anchor:
identify when commercial terms should be reopened
Balancing Cost and Approval Rates
Anchor:
calculate how much approval performance can justify a higher processing price
How Multi-PSP Competition Affects Pricing
Anchor:
understand how provider alternatives affect commercial leverage
Payment Method Fees / Method Economics
Anchor:
compare payment-method economics across the actual checkout mix
Supporting visual
PSP Pricing Comparison Model
Design as a three-column procurement worksheet.
Across the top:
QUOTE 1
Flat/blended
QUOTE 2
Interchange-plus
QUOTE 3
Percentage + fixed fee
Down the left:
Underlying/payment cost
PSP/acquirer markup
Percentage charge
Fixed transaction charge
Method-specific cost
Cross-border cost
FX
Ancillary cost
Platform/account fees
Volume tiers
Minimum commitment
Then show:
CURRENT CASE
annual cost
effective rate
cost/transaction
GROWTH CASE
annual cost
effective rate
cost/transaction
DOWNSIDE CASE
annual cost
effective rate
minimum shortfall
Bottom callout:
Compare the same merchant portfolio—not the percentages printed at the top of three proposals.
Image alt text
PSP Pricing Comparison Model normalizing flat-rate, interchange-plus and percentage-plus-fixed-fee payment-provider quotes into annual merchant cost, effective rate, cost per transaction, volume tiers and minimum exposure across current, growth and downside scenarios.
Measurement plan
Track for every finalist:
Total annual provider cost
Primary commercial comparison metric.
Effective rate
Included provider cost ÷ eligible payment volume
Cost per transaction
Included provider cost ÷ transaction count
Provider markup
Where separately observable.
Fixed-fee burden
Total fixed transaction fees ÷ total annual provider cost
or express separately in dollars and basis-point equivalent.
Minimum shortfall
Contracted minimum − modeled qualifying spend
where positive.
Scenario variance
Difference between modeled current/growth/downside cost.
Gross commercial saving
Current normalized cost − proposed normalized cost
Then hand the result to the wider provider-economics model for implementation and performance analysis.
Authoritative source recommendations
Highest-value merchant evidence
Use first:
Merchant provider contracts.
Commercial pricing schedules.
Merchant processing statements.
Transaction-level payment data.
Provider proposals.
Merchant finance/procurement model.
These should drive the actual quote comparison.
Visa
Use official Visa documentation for the distinction between interchange reimbursement fees and the merchant discount arrangement rather than treating the published interchange table as the merchant's complete cost.
Mastercard
Use current Mastercard interchange documentation for the role of interchange within the broader merchant discount rate and for the fact that applicable interchange can depend on transaction characteristics.
Proposed author and reviewers
Author:
Payment procurement reviewer:
[Named reviewer]
Merchant finance analyst:
[Named reviewer]
Payments pricing reviewer:
[Named reviewer]
Acquiring specialist:
[Named reviewer where pass-through card-cost modeling remains]
International payments reviewer:
[Named reviewer where cross-border/FX assumptions are material]
Last reviewed:
[Publication date]
Recommended first-hand contribution
The most useful proprietary contribution would be an approved anonymized procurement model where:
three differently structured quotes were normalized;
the lowest percentage was not the lowest annual cost;
rankings changed under one stress scenario;
the resulting model produced a more specific negotiation or procurement decision.
Do not invent the case.
Pricing fact-check items
Before publication verify for every quoted model:
Pricing model.
Percentage charge.
Fixed fee.
Provider/acquirer markup.
Underlying-cost treatment.
Payment-method charges.
Cross-border additions.
FX scope.
Ancillary charges.
Platform/account fees.
Volume tiers.
Minimum commitment.
Provider-share commitment.
Effective date.
Contract term.
Public versus negotiated status.
Taxes where relevant to comparison.
Benchmark fact-check items
For every benchmark verify:
merchant segment;
geography;
transaction value;
transaction count;
payment method;
card/issuer mix;
domestic/international mix;
currency;
pricing model;
period;
cost scope;
source;
whether public or negotiated.
Do not use an anecdotal merchant quote as an authoritative benchmark.
Volume-tier fact-check items
Verify:
qualifying volume definition;
monthly versus annual measurement;
threshold;
blended versus marginal treatment;
timing of repricing;
retroactive versus prospective application;
excluded payment methods;
excluded markets;
required provider share;
commitment period.
Contract fact-check items
Verify:
minimum spend;
minimum volume;
exclusivity;
provider-share requirements;
term;
renewal;
termination;
repricing clauses;
price-review clauses;
bundled-service dependencies.
A lower rate obtained in exchange for reduced flexibility should not be described as a pure saving.
Approval/performance fact-check items
Where performance enters the wider procurement decision, verify:
cohort;
geography;
payment method;
issuer/card mix;
transaction value;
provider/acquirer;
fraud rules;
authentication;
retry behavior;
period.
Do not insert assumed provider-performance uplifts into the pricing table.
Regulatory and network-rule flags
This specific article is primarily commercial.
Still verify any proposal elements affected by:
network rules;
regulatory pricing limits;
surcharging;
routing;
merchant steering;
contractual exclusivity.
Visa and Mastercard's official materials distinguish network-set interchange mechanics from merchant/acquirer commercial pricing, reinforcing why contract and cost layer should not be conflated.
Disclaimer:
This article provides general information and does not constitute legal, regulatory, financial, accounting, procurement, or commercial advice. Merchants should verify current provider terms, payment-network rules, contractual commitments and applicable regulation with qualified advisers and relevant payment partners.
Amber-flag claims
“1.4% is cheaper than 1.9%.”
Not without normalizing fee scope and merchant mix.
“Interchange++ + 25 bps means the merchant pays 0.25%.”
Incorrect if underlying costs are additional.
“Interchange is the merchant's full card-processing price.”
Too broad.
Visa and Mastercard distinguish interchange from the broader merchant/acquirer commercial cost.
“A blended price is always worse than interchange-plus.”
Unsupported.
Merchant mix determines the result.
“Interchange-plus is always more transparent and therefore cheaper.”
Transparency and total cost are separate questions.
“Higher volume automatically qualifies for a lower rate.”
Contract mechanics determine this.
“The lowest quote is the best PSP.”
Commercial price does not determine full provider economics.
“Public pricing proves what an enterprise merchant should pay.”
Unsupported without comparable merchant circumstances.
“Provider X has better pricing.”
Requires current comparable quotes and a defined merchant portfolio.
Do not publish without merchant-specific evidence.
Do not publish without current applicable terms.
Current card-pricing structures.
Pass-through versus bundled underlying-cost treatment.
PSP/acquiring markup terminology.
Fixed transaction fees.
Local-method pricing.
Market-specific pricing.
Cross-border commercial additions.
FX pricing.
Platform/account charges.
Relevant ancillary charges.
Volume tiers.
Tier mechanics.
Minimum commitments.
Provider-share commitments.
Pricing-review clauses.
Merchant-specific negotiated terms.
Current acquiring options.
Reporting fields required for cost normalization.
Current payment-method coverage.
Merchant-specific performance evidence where used.
Approved procurement case study.
Approved negotiated-savings evidence.
Named payments-pricing reviewer.
Named commercial/legal reviewer where necessary.
Effective dates.
Cluster sameness audit
Field
This article
Title
Comparing PSP Pricing: How to Normalize Provider Quotes Before Choosing a Deal
Opening device
Three incompatible quote structures land in procurement
Merchant pricing problem
Headline rates lack a common denominator
Addressable cost
Provider commercial cost in competing proposals
Merchant leverage
Comparable alternatives and transaction-mix evidence
Pricing lever
Commercial provider selection / negotiation
Baseline
Same merchant transaction portfolio
Performance guardrail
Approval/completion reviewed separately
Primary format
Normalized PSP quote comparison
Unique evidence anchor
Different pricing structures can reverse headline ranking
Editorial position
Compare modeled annual cost before headline percentages
Assumption challenged
Lowest percentage = cheapest provider
Merchant decision
Which commercial proposal costs least under realistic scenarios?
Original framework
PSP Pricing Comparison Model
Primary metric
Total annual provider cost
Secondary metrics
Effective rate, cost/transaction, minimum exposure, scenario variance
Closing device
Proposal-comparison scenarios + procurement checklist
CTA
Model quote against actual merchant mix
Generic FAQ
None
Cannibalization safeguards
How to Negotiate PSP Pricing owns negotiation tactics.
When to Renegotiate Payment Fees owns timing triggers.
Volume-Based Payment Pricing owns tier and volume-leverage mechanics.
Payment Cost Benchmarking owns benchmark construction.
This article alone owns commercial quote normalization.
Routing Payments by Cost owns cost-aware transaction routing.
Least-Cost Routing Explained owns least-cost routing mechanics.
Balancing Cost and Approval Rates owns cost-versus-approval break-even.
Optimizing Payment Methods by Margin owns method profitability.
How Multi-PSP Competition Affects Pricing owns competitive-leverage effects.
Why the Cheapest PSP May Cost More remains in True Cost and Net Revenue and owns the broader economic-provider decision.
Editorial standard
The final procurement question should never be:
“Which PSP quoted the smallest number?”
Nor should it be:
“Which pricing model sounds most transparent?”
The decision should be:
When every proposal is applied to the same merchant transactions, payment methods, countries, currencies and realistic volume scenarios, what does each provider cost annually—and which commercial assumptions could change that ranking?
That is the article's unique territory.
It converts an RFP from a collection of percentages into an auditable financial model—and gives procurement a defensible basis for selecting, challenging, or renegotiating the deal.
Need help narrowing down payment options?
Answer a few questions about your business and compare the capabilities that matter to you.
Explore matching options ↗