Skip to content

Build

How to Build a Payment Gateway for a SaaS Platform

Vertical software companies sit on a payments opportunity. Their customers, gyms, clinics, schools, booking businesses, already run their day inside the software, and many of them still take payments somewhere else. Bringing payments into the product keeps customers longer and adds revenue on every transaction they process.

There are four ways to do it, and only one of them means building a payment gateway for a SaaS platform yourself. This page compares all four, sets out what has to be built into the product in every case, and shows the revenue math that usually decides the choice.

Four models for embedded payments in SaaS

The models differ in how much you control, how much you earn and how much risk you carry. Each step down the table adds all three.

Model What you do What you earn What you carry
Referral Send customers to a payment provider A referral fee or small share Almost nothing
Integrated partner A provider powers payments inside your product A share of the processing margin Support and some onboarding work
Payment facilitator You onboard customers as sub-merchants under a sponsor acquirer Most of the margin Underwriting, chargeback liability, registration
Your own PSP You run a licensed payment business on your own gateway The full margin, plus other payment products A license, acquirer contracts, operations

Many SaaS companies start in the first two rows and move down as volume grows. Moving later is easier if the product was built for it from the start.

What embedded payments for SaaS have to include

Whatever the model, customers should never feel they're leaving your product to get paid. That puts a few features on your side of the line.

  • onboarding from inside the product, with the payment provider's checks running through an API
  • a checkout for your customers' own clients, styled like your product
  • payment status, payouts and fees visible inside your interface
  • refunds and disputes that your customers can handle without a second login
  • webhooks into your product, so a paid invoice or a failed charge updates the right record

The last item is easy to underestimate. Payments touch almost every object in a vertical SaaS product, from appointments to invoices to memberships.

The revenue math

Payments revenue comes from the gap between what your customers pay per transaction and what processing costs you. A small difference per transaction adds up over a customer base.

Take a hypothetical platform with 2,000 customers, each processing $20,000 a month. That's $40 million a month in volume. At a margin of 0.3 percentage points, it's $40,000,000 x 0.3% = $120,000 a month, or $1.44 million a year, before costs. The model you choose decides how much of that margin you keep and how much work and risk come with it.

How to start a fintech SaaS payment gateway company

Some SaaS companies go further and turn payments into a business of their own, serving merchants beyond their software's users. That's a PSP launch, and it follows the PSP path: a license where your model needs one, acquirer contracts, a gateway and a merchant back office.

The gateway is the part you can license. Building it adds a year or more before the first payment, while licensing lets the team focus on what the SaaS company knows best, its customers' workflows.

Running a payment gateway for a SaaS platform on ours

Our white label gateway is built for the integrated and PSP models. Sub-merchant onboarding, risk scoring, monitoring and settlements are available through the API, so onboarding can live inside your product. Split payments and payouts across several sellers and providers are supported, and webhooks keep your product in sync with every payment event.

The checkout, the customer dashboard and the reports carry your brand. On SaaS, a first live payment usually follows within a week when the connectors you need are ready. Becoming a payment facilitator adds underwriting and liability on top, which a PayFac platform has to support.

Questions

How do SaaS companies make money from payments?

By keeping part of the gap between what their customers pay per transaction and the processing cost. A referral earns little, an integrated partnership earns a share, and a PayFac or own PSP earns most of the margin with more risk and work.

Should a SaaS platform build its own payment gateway?

Rarely from scratch. Licensing the gateway and building the payment experience into the product gives most of the value without a year-long build.

Can an existing PSP move from a SaaS gateway to self-hosting?

It depends on the vendor. Ours runs the same platform as SaaS, in your own cloud account (about 30 days to set up) or on your own servers (about 60), so ask about moving between them when you scope the project.

What's the difference between embedded payments and a payment facilitator?

Embedded payments describes the experience inside the software. A payment facilitator is one way to deliver it, where the platform onboards customers as sub-merchants under its own registration.

Add payments to your platform

Tell us about your customers and their payment volumes, and we'll show which model fits and how it runs on our platform.