How SaaS platforms should manage a payments buy rate

A practical guide to payments pricing, margin, reconciliation, risk, and governance at scale

For SaaS platforms that enable merchants to accept payments, a buy-rate model gives the platform control over merchant pricing. The platform purchases payment services at a contracted wholesale rate, generally consisting of network costs plus a provider markup, and sets the rate charged to merchants.

Offering payments often begins as an integration project and becomes a strategic business model as adoption grows. Under a buy rate, the platform can retain the difference between merchant revenue and its processing costs. That spread can drive gross profit and product adoption, but it can erode quickly if the buy rate is treated as a static contract term rather than an operating model.

The mechanics vary by provider, risk allocation, geography, and flow of funds, but the responsibility is consistent: the platform owns the pricing decision and its economics. Strong platforms manage the full cost stack, pricing architecture, exceptions, reporting, and governance rather than relying on one blended percentage.

Key takeaways

A payments buy rate is only the starting point. Merchant pricing should reflect the complete cost of the offering: network fees, provider fees, payment products, risk, losses, and operational expenses.
A limited number of clearly defined merchant segments is generally easier to manage than a single universal rate or hundreds of custom exceptions.
Accurately measuring payments margin requires ongoing reconciliation across provider reports, balance or ledger activity, and internal billing data.
Every material pricing change should have a clear owner, defined approval guardrails, thorough testing, and post-launch monitoring.
Surcharging can be a strategic lever for buy-rate platforms to offer additional value to merchants

A five-step framework for managing a payments buy rate

1. Decide whether your platform is ready to manage a buy rate

A payments buy rate is the underlying price a provider charges a software platform for processing and related services, including products such as fraud tools, terminals, payouts, and alternative payment methods. The platform sets the merchant price, and the difference between merchant revenue and total underlying costs is its payments margin.

Under revenue share, the provider generally controls merchant pricing and pays the platform an agreed share of the economics. Under a buy rate, the platform controls pricing and packaging and gains more visibility into network costs, but assumes greater responsibility for variable costs, negotiations, exceptions, loss allocation, reporting, and reconciliation.

A buy rate is therefore not automatically the more profitable model. It offers more control over the inputs, but it also comes with significantly more operational responsibility and complexity.

2. Model the full payments cost stack, including costs beyond successful payments

The most common mistake in buy-rate pricing is comparing the merchant’s rate only with the processor’s headline markup. A complete model should capture every cost that affects contribution margin, including:

Interchange and card-network assessments, which vary by card type, funding source, merchant category, geography, and payment channel.
Processor volume and per-request fees, including authorization fees on failed payment attempts.
Platform, account, and product fees, including onboarding, active-account, payout, fraud, and optimization tools.
Refunds, disputes, cross-border processing, currency conversion, and local payment methods.
The platform’s operating costs and loss exposure, including underwriting, risk management, reconciliation, bad debt, and support.

Start with merchant payments revenue and subtract network, provider, and product fees, refund and dispute leakage, and realized losses. The result is the platform’s payments contribution margin.

Fixed fees disproportionately affect low-value or high-attempt transactions, so model margin using transaction distributions rather than a single average. At minimum, analyze average order value, authorization-to-capture ratio, payment channel (card present versus card-not-present), funding type (debit versus credit), cross-border activity, payment method, and refund and dispute rates. Evaluate the results by merchant and segment because portfolio averages can conceal losses.

Some costs occur without a successful payment and therefore without platform-fee revenue.

Decide:

Who absorbs each cost: the platform, the merchant, or the payment provider?
How will the cost be recovered, if at all: through a separate debit, invoice billing, or platform earnings?
What policy applies to refunds, disputes, failed attempts, and negative balances?

Document these decisions in a single source of truth. Refund and dispute treatment, provider configurations, API overrides, contracts, and accounting logic must align; otherwise, the platform may price one way and settle another.

3. Segment merchant pricing strategically

Most platforms should begin with a default rate for a small pilot group, then add a limited number of segments based on merchant feedback, market benchmarks, observed network costs, and transaction performance. The goal is to prevent materially different cost profiles from subsidizing one another, not to negotiate a unique contract with every merchant.

Useful segmentation dimensions include:

Software plan and merchant value: Premium software tiers may include more favorable payments pricing, while entry-level tiers carry a higher rate.
Merchant scale: Higher-volume merchants may qualify for lower pricing, but only after the platform confirms that the proposed rate still meets its margin requirements.
Payment method: Cards, ACH, digital wallets, buy now, pay later, and local payment methods have different cost structures and value propositions.
Transaction profile: Card-present versus card-not-present activity, credit versus debit mix, card brand, average order value, and recurring versus one-time payments can all affect cost.
Geography: Merchant location, cross-border activity, and currency conversion can materially change the platform’s underlying economics.
Risk profile: Higher-risk merchants may require different pricing, reserves, payout schedules, underwriting standards, or contract terms rather than a simple increase in basis points.

Some payment providers offer rule-based pricing tools and merchant groups. Others require the platform to apply pricing through transaction-level API parameters, account configuration, or an internal pricing engine. Regardless of the implementation, the intended rate, applicable merchant segment, and reason for every override should be visible and auditable.

Every pricing model also needs a fallback. A transaction that fails to match a conditional rule should not receive a zero or underpriced platform fee. Set an intentionally conservative default rate and monitor unmatched transactions through a dedicated exception process.

Finally, payments pricing should be considered alongside the platform’s broader software packaging and payments monetization strategy. Some platforms intentionally keep payments pricing low, or even operate payments as a loss leader, to drive adoption and monetize the core software product. Others reduce software fees to increase payments adoption and generate more payments margin. Neither approach is universally correct. The platform should measure total merchant contribution and make the tradeoff deliberately.

4. Evaluate payments margin on the timing of the cost’s occurrence, not just the charge itself

Buy-rate economics are asynchronous. Payments occur at one moment, while final interchange costs, batched fees, payouts, monthly network fees, and true-ups may arrive later. A payment transaction alone is therefore not a margin report.

Reconcile provider fee reports, balance or ledger activity, settlement exports, and internal billing data in a data warehouse or internal ledger. The process should also reopen or adjust prior periods when late costs arrive.

A practical reporting cadence includes:

Daily: Check for missing platform fees, unmatched pricing rules, unusual authorization volume, and negative balances.
Monthly: Reconcile revenue, network and provider fees, true-ups, refunds, disputes, losses, and ending balances.
Quarterly: Review margin by segment, cost-mix changes, concessions, and repricing opportunities.

Measure both take rate and margin in dollars, by merchant and segment. A small basis-point improvement on a large merchant may matter more than a high percentage margin on a small one.

5. Put governance around every merchant rate change

Buy-rate programs break down when pricing is shared across teams without clear ownership. A commercial exception, product change, or API override can affect margin long before finance or support sees the result.

Assign responsibility across three areas:

Financial ownership: Finance maintains the cost model, target margins, reconciliation, and reporting; risk defines underwriting, monitoring, reserves, and loss escalation.
Product and technical ownership: Product defines packaging, merchant experience, and exception policies; engineering maintains the pricing source of truth, ledger behavior, and observability.
Commercial ownership: Sales follows approval guardrails for concessions, while support receives merchant-facing explanations and escalation paths before launch.

Test every material pricing change before rollout. Back-test the economics, validate edge cases, stage the release, and monitor actual results.

A strategic lever: where credit card surcharging fits

A surcharging program can support a buy-rate strategy by changing how merchants experience card-acceptance costs. On eligible credit card transactions, it allows merchants to pass some or all of those costs to cardholders.

This can give a platform more flexibility to set a sustainable rate, reduce pressure for unsustainably low merchant pricing, keep payment volume on the platform, and support premium packaging or another revenue stream.

Surcharging does not replace buy-rate management. Not every payment is eligible, and platforms still incur and may pass on costs for debit and prepaid cards, failed authorizations, refunds, disputes, payouts, and other services. It also requires card-network and jurisdictional compliance, disclosures, refund policies, and merchant-level configuration.

Payments buy-rate launch checklist

Before launching or materially changing a buy-rate program, confirm that the platform has:

☐An executed provider contract covering tiers, minimum commitments, product fees, and post-promotional pricing.
☐A default merchant rate, approved segmentation, and a conservative fallback configured in one authoritative pricing engine with controlled overrides.
☐Documented policies for refunds, disputes, failed attempts, negative balances, payouts, losses, merchant-facing terms, and concession approvals.
☐Daily reporting and monthly reconciliation that incorporate late costs and measure margin by merchant and segment.
☐Sandbox or pilot testing for representative merchants and edge cases, supported by active risk monitoring and clear ownership.

If surcharging is in scope, separately document eligibility, card-network and jurisdictional requirements, surcharge limits, disclosures, debit and prepaid exclusions, refund treatment, merchant configuration, and go-to-market messaging.

Frequently asked questions about payments buy rates

What is a buy rate in payment processing?

A buy rate is the underlying price a payment provider charges a platform for processing and related services. The platform then sets the rate merchants pay and may retain the difference after all applicable costs.

What is the difference between a buy rate and revenue share?

With revenue share, the payment provider generally controls merchant pricing and shares part of the economics with the platform. With a buy rate, the platform controls merchant pricing and retains the spread, but assumes more responsibility for pricing, exceptions, reporting, reconciliation, and governance.

How should a platform calculate payments margin?

Start with merchant payments revenue, then subtract network costs, provider and product fees, refund and dispute leakage, and realized losses. Calculate the result by merchant and segment as well as in aggregate.

Which costs are commonly missed in buy-rate models?

Commonly missed costs include failed authorization fees, active-account charges, payouts, fraud tools, network tokens, card account updater, cross-border fees, currency conversion, refunds, disputes, and the platform’s own support, loss, and reconciliation costs.

How often should a platform review buy-rate pricing?

Monitor exceptions and sharp margin changes weekly, reconcile complete economics monthly, and review merchant pricing and segmentation at least quarterly. A major contract, product, geographic, or payment-method change should trigger an additional review.

How does credit card surcharging affect a payments buy-rate strategy?

Surcharging can help merchants offset eligible credit card acceptance costs, giving platforms more flexibility to establish sustainable pricing. However, it does not replace buy-rate management because many costs, including debit and prepaid transactions, failed authorizations, refunds, disputes, and other payment services, may not be recoverable through a surcharge. Platforms must also account for card-network rules and applicable laws.

How Yeeld helps software platforms manage payments pricing

Yeeld helps software platforms design, implement, and optimize embedded payments programs, whether they are evaluating a buy rate, moving from revenue share, or improving an existing model. We connect commercial strategy to the product, technical, and operational systems needed to protect margin at scale.

When surcharging is in scope, Yeeld helps model its economic impact, design merchant pricing and go-to-market packaging, and implement eligibility, calculation, disclosure, refund, and reporting logic across payment flows.

Yeeld’s surcharging technology helps merchants recover eligible credit card acceptance costs while platforms protect payment volume and support a sustainable buy-rate model.