Embedding Payments

/

Most Payments Solutions Weren't Built for Platforms. Here's Why That Matters.

BY Spencer Nichini

Forward logo under the headline "Most payments solutions weren't built for platforms." in white text inside a gold circle on a dark navy background.

If you operate a software platform, you've probably heard from plenty of payments companies. Stripe Connect, Adyen for Platforms, and a long list of others all pitch software companies and most of them call themselves platform-friendly.

Very few were actually purpose built for platforms.

That difference sounds like a branding detail. It isn't. It decides how much of the payments business you actually own, and in the end, how much your payments business is worth to you.

What does "bolted on" look like?

Most payments companies weren't built with software or AI platforms in mind. Some started by processing payments serving retailers, others focused on large enterprises or small e-commerce businesses. Platforms came later, as an offering bolted onto a business originally designed for someone else.

You can usually see the difference in how these programs operate:

  • You don't control pricing. The processor dictates what your customers pay, including the introduction of unexpected or "junk" fees, leaving you with little flexibility.
  • The branding isn't yours. Your customers see the processor's name on statements, dashboards, and support interactions instead of your own.
  • Your revenue share is an afterthought. Your economics are determined by what's left after the processor has optimized for its own business.

The limitations become even more apparent as your business grows. When a customer needs custom pricing, a different payout configuration, or help resolving a dispute, you're constrained by a program that wasn't designed to give you that flexibility. Your team ends up explaining someone else's rules to your own customers.

That doesn't mean the technology is bad. In many cases, it works just fine. The problem is that the business model wasn't built around you.

Instead of owning the customer experience, you're handing your customers off to a processor whose priorities may not align with yours. To them, your platform is just another account in a massive portfolio.

You're building a payments business. They're treating you like a referral source.

What does "built for platforms" look like?

A payments company built for platforms takes a fundamentally different approach. The entire payments infrastructure, from card networks and acquiring banks to the platform and its end customers, is designed around the needs of the software company.

That changes what you get:

  • Control over pricing. You decide what your customers pay for payments, just as you control what they pay for your software.
  • Your brand, front and center. Payments looks and feels like a seamless part of your product, because to your customers, it is.
  • The majority of payments revenue. The economics are structured to maximize revenue for your platform, rather than leaving you with a small referral fee.
  • Help driving payments adoption. Simply enabling payments doesn't mean customers will switch. A partner built for platforms actively helps convert your existing customer base through white-label outreach and adoption programs, driving more payment volume through your platform.
  • A dedicated GM of Payments. An experienced partner focused on helping you operate, optimize, and grow your payments business.

None of this should be extraordinary. It's what happens when a payments company is purpose-built for platforms, rather than treating them as just another customer segment.

The relationship is fundamentally different. You own the payments business. Your partner provides the infrastructure, expertise, and support to help you grow it.

Why does the difference matter to a founder?

It comes down to three things: economics, control and leverage.

Economics

With a bolted-on payments program, you're typically compensated like a referral partner. You receive a small share of the revenue, while the processor retains the majority of the economics.

With a partner built for platforms, you gain transparent buy rates and the ability to turn payments into a meaningful revenue stream. Most platforms start with fewer than 20% of their customers processing payments through their software, while successful programs can exceed 70% adoption.

Combine higher adoption with retaining the majority of payments revenue, and payments can go from a minor line item on your P&L to a revenue stream that rivals or even exceeds your software revenue.

A referral fee is easy to overlook. A meaningful revenue stream gets forecasted, reported to the board, and managed as a core part of the business.

Control

Whoever controls pricing and branding has significant influence over the customer relationship. When your processor dictates pricing and the payments experience, someone else is making decisions that directly impact your customers, even though payments happens inside your product.

When you own pricing and branding, payments becomes a natural extension of your software. You decide how it's packaged, priced, and delivered to each customer.

That flexibility becomes increasingly valuable as you grow. Larger customers have more complex needs, and you want the ability to say yes rather than ask your processor for permission.

Leverage

AI is making software features easier to replicate. A payments feature bolted onto your product is just as easy to copy because your competitors can integrate the same solution.

But owning how your customers get paid is much harder to replicate or replace.

When customers process payments through your software, under your brand and on your pricing, switching platforms means changing more than just their software. It means disrupting how they accept payments, manage transactions, and run their business.

That's payments as a moat, and it's a competitive advantage that AI alone can't replicate.

What should you ask a potential payments partner?

Before choosing a payments partner, ask these five questions:

  • Who controls my customers' pricing? If you're not the one setting prices, you don't have full control over your payments business.
  • What is my actual cost of payments? If the answer is simply "you receive X% of revenue," that's a red flag. Without transparent buy rates, you don't know what costs are deducted before your share is calculated. Worse, if you increase prices for your customers, your processor benefits from the additional revenue generated by your efforts.
  • Who helps drive payments adoption? If the answer is "your team," be prepared to dedicate an internal team to managing and growing your payments business. If you're not ready to absorb that cost, look for a partner like Forward that provides white label conversion resources. After all, adoption is what ultimately drives payments revenue.
  • Who is my dedicated point of contact? There's a big difference between submitting tickets to a support queue and having an experienced payments expert who understands your business and is accountable for helping it grow.
  • Can I eventually become a fully registered PayFac without having to reapply my customers? Customer migration is one of the most disruptive parts of switching payments providers. The right partner gives you a path to take on more responsibility and control as you scale, without forcing you to start over.

The answers will quickly reveal whether a payments partner was purpose-built for software platforms or simply added platforms as another customer segment.

You already own a payments business. Get paid for it.

See what your volume is worth.

Bolted-on vs built-for payments FAQ

What are bolted-on payments for software platforms?

Bolted-on payments are payment programs that a processor added for software platforms after first building its business for retailers, large enterprises, or e-commerce businesses. According to Forward, the signs are consistent: the platform does not control customer pricing, the processor's brand shows up on statements and dashboards, and the platform's revenue share is whatever is left after the processor optimizes for its own business.

What does a payments partner built for software platforms provide?

A payments partner built for software platforms designs its whole stack, from card networks and acquiring banks to the platform and its customers, around the software company. Forward describes five results: the platform controls customer pricing, payments carries the platform's brand, the platform keeps the majority of payments revenue, the partner helps convert the existing customer base through white-label outreach, and the platform gets a dedicated GM of Payments.

How many of a software platform's customers typically adopt embedded payments?

Most software platforms start with fewer than 20% of their customers processing payments through their software, while successful embedded payments programs can exceed 70% adoption. Forward's view is that adoption is what ultimately drives payments revenue, which is why Forward provides white-label conversion help to bring a platform's existing customers onto payments instead of leaving adoption to the platform's own team.

What questions should a software platform ask before choosing a payments partner?

Forward recommends five questions before choosing a payments partner: Who controls my customers' pricing? What is my actual cost of payments, with transparent buy rates? Who helps drive payments adoption? Who is my dedicated point of contact? Can I eventually become a fully registered payment facilitator without having to reapply my customers? The answers show whether a partner was built for software platforms or added platforms later.

Why are embedded payments a moat for software platforms as AI makes features easier to copy?

AI is making software features easier to copy, and a bolted-on payments feature is easy to copy too because competitors can integrate the same solution. Forward argues that owning how customers get paid is much harder to replace. When customers process payments through a platform under its brand and pricing, switching software means disrupting how they accept payments and run their business. That makes embedded payments a moat.

Subscribe to Forward

Share article

Build payments into your product

Want to learn more or apply this specifically to your business? Speak to a payments expert today.

clouds fill