The number most vendors won't give you until you're already two months into the sales process.

If you've ever tried to get a straight answer on what it costs to add embedded payments to a vertical SaaS platform, you know the experience: vague ranges, "it depends" answers, and a request to get on a call with a solutions engineer before anyone will give you real numbers.

Some of that complexity is genuine — costs do vary meaningfully based on volume, vertical, and program structure. But a lot of it is deliberate obfuscation. Payment processors and PayFac-as-a-Service providers have strong incentives to get you into a sales process before you have enough information to negotiate effectively.

This article lays out the real cost structure across all four embedded payments models. You should be able to read this and walk into any vendor conversation with a clear understanding of what you're paying for, what's negotiable, and what's a red flag.

The Two Categories of Cost

Before we get into model-specific numbers, it's worth separating embedded payments costs into two categories that often get conflated: implementation costs and ongoing operating costs. They're different decisions with different timelines and different ROI calculations.

Implementation costs are one-time or ramp-period expenses — the investment required to build the program, integrate the technology, and reach steady-state operations. Operating costs are ongoing — the fees, splits, and costs that repeat every month as long as the program is running.

Most vendors lead with implementation costs because those are the scariest-sounding numbers. Smart operators focus first on operating costs because those determine the long-run economics of the business.

Model 1: ISV Referral — The Low-Cost, Low-Return Option

Implementation Costs

An ISV referral arrangement has minimal implementation cost — typically $5,000 to $15,000 for basic integration work, legal review of the referral agreement, and merchant communication. You're not building payment infrastructure; you're connecting merchants to a partner's infrastructure.

Ongoing Costs

There are essentially no ongoing costs in a referral model. You're receiving a share of the economics the processor earns. If volume drops, your revenue drops but so does your cost basis — there's no fixed cost structure to worry about.

The Real Cost

The real cost of the ISV referral model isn't a line item — it's opportunity cost. You're trading long-run economics for short-run simplicity. At meaningful volume, the difference between referral economics (5–15 basis points) and PayFac-lite economics (15–40 basis points) compounds into a significant gap.

Model 2: Gateway Integration / Enhanced Residuals

Implementation Costs: $20,000–$75,000

The primary implementation costs in a gateway model are engineering time and integration work. If you're using a well-documented gateway API, a competent engineering team can complete the integration in 4 to 12 weeks. At typical fully-loaded engineering costs, that's $20,000 to $60,000 in internal labor.

Add legal review of the gateway agreement ($2,000–$5,000) and any UX/design work for the payment flow, and total implementation cost typically lands in the $25,000–$75,000 range.

Ongoing Costs

Gateway models have three ongoing cost components. First, the gateway fee itself: usually $0.05–$0.15 per transaction, or a small monthly platform fee. Second, passthrough costs from the card networks — these run 0.10%–0.14% of volume and can't be negotiated. Third, your processor spread — the margin your processor earns above interchange. This is your primary negotiating lever.

The processor spread is where you need to pay close attention. A spread of 15 basis points on $30M in volume costs you $45,000 per year. A spread of 25 basis points on the same volume costs you $75,000. That $30,000 annual difference is entirely negotiable, and most platforms either don't negotiate it or don't go back to renegotiate as their volume grows.

What's Negotiable

In a gateway model, the processor spread is your primary negotiating lever. Passthrough costs aren't negotiable (they're set by Visa and Mastercard). Gateway transaction fees have some flexibility but less than the spread. If your volume has grown meaningfully since you signed your agreement, you should be renegotiating.

Model 3: PayFac-Lite (Sponsored PayFac)

Implementation Costs: $50,000–$200,000

PayFac-lite is where implementation costs start to get serious — but also where the economics justify them. The major cost components are:

Ongoing Costs

The ongoing cost structure in a PayFac-lite model is more complex than a gateway model. You're paying your PayFac-as-a-Service provider a platform fee (usually $500–$2,000/month), a per-transaction processing fee, and a share of the net economics. The economics you retain depend heavily on how your agreement is structured.

A typical PayFac-lite economics structure: the provider earns 40–60% of the net spread above passthrough costs, and you retain 40–60%. On $50M in annual volume with a net spread of 40 basis points, that's $200,000 gross margin to split. Your share — at a 50/50 split — is $100,000 per year.

This is also where chargeback costs matter. In a PayFac-lite model, you share in the chargeback liability. Depending on how the agreement is structured, you may absorb losses above a certain threshold. Understand this clearly before you sign.

What's Negotiable

The economics split between you and the PayFac-as-a-Service provider is negotiable — and your negotiating leverage increases with volume. If you're bringing $20M+ in volume to a provider, you should be negotiating for a more favorable split than their standard terms. The major providers — Finix, Payrix, Payroc — all have pricing flexibility at meaningful volume levels.

Model 4: Direct PayFac

Implementation Costs: $500,000–$2,000,000+

Direct PayFac is in a different cost category entirely. The primary cost components are: registration fees with Visa and Mastercard ($5,000–$10,000), dedicated payments engineering (typically 2–4 full-time engineers for 18–24 months), legal and compliance infrastructure, underwriting and risk systems, and reserves capital.

When you add it all up — internal labor, systems, legal, compliance, and reserve requirements — most platforms building a Direct PayFac from scratch spend $500,000 to $2M before they reach steady-state operations.

Ongoing Costs

The ongoing cost structure for a direct PayFac is essentially that of running a small financial services business: payments operations staff, compliance monitoring, risk management, chargeback handling, and the ongoing cost of regulatory relationships.

The reason platforms build to Direct PayFac despite these costs is that the economics are proportionally larger. On $200M in annual volume, the difference between a PayFac-lite take rate of 25 basis points and a Direct PayFac take rate of 60 basis points is $700,000 per year. At that scale, the investment pays back.

Who Should Actually Do This

Direct PayFac is the right answer for a narrow set of platforms: those with $100M or more in annual payment volume, strong technical teams, and the organizational capacity to run a payments business alongside a software business. For everyone else, the math almost never works.

We see early-stage platforms pursue Direct PayFac because it sounds like the most serious, most sophisticated option. That's usually a mistake that delays revenue by 18 months and consumes capital that could have been deployed in the core product.

The Hidden Costs Everyone Forgets

Beyond the model-specific costs above, there are recurring costs that apply regardless of which path you choose — and they're almost always underestimated in initial business cases.

Merchant Support

When you embed payments, you become the first line of support for payment-related questions. How long does a settlement take? Why was this transaction declined? What do I do about this chargeback? Your current support team isn't trained for this, and payment support tickets are higher-effort than typical software support tickets. Budget for training and potentially for headcount.

Compliance Overhead

PCI DSS compliance costs money — security scans, annual assessments, potential pen testing. At the gateway level, you're mostly protected by your processor's compliance posture, but you still have obligations. At the PayFac-lite level, you're taking on more compliance responsibility. Budget $5,000–$25,000 annually depending on your volume and risk profile.

Integration Maintenance

Payment APIs change. New card brands get added. Regulations update. The ongoing engineering cost of maintaining a payments integration isn't zero — it's typically 10–20% of the original build cost per year. Factor this into your ROI model.

How to Think About the ROI

The right way to evaluate embedded payments cost is not "can we afford to build this" but "what is the payback period relative to the annual revenue opportunity."

A gateway integration that costs $50,000 to build and generates $80,000 in net annual payment revenue pays back in about 7 months. After that, it's essentially pure margin on existing volume. That's a strong business case.

A PayFac-lite program that costs $150,000 to implement and generates $200,000 in net annual revenue at steady state has a similar profile. The implementation looks expensive until you model the 5-year return.

The programs that don't have good ROI are the ones where the implementation cost is out of proportion to the volume — usually because the platform tried to build too sophisticated a program too early, or because they signed a processor agreement with economics that were too favorable to the provider.