

Short answer: A software platform can add payments in three ways. It can partner with a payment company and refer its customers, which is the least work and the least revenue. It can build payments into its product on top of a provider that carries the regulated work, which is what most platforms do. Or it can become a registered payment facilitator, which gives the most control and revenue and brings the most cost, staffing and liability. Most platforms start with the second route and move to the third only at very large volume, if ever.
The three routes at a glance
| Partner and refer | Build on a provider's platform product | Become a payment facilitator | |
|---|---|---|---|
| What you do | Send customers to a payment company | Embed that provider's onboarding, checkout and payouts in your product | Register through an acquiring bank and run payments for your customers yourself |
| Who signs up and checks your customers | The payment company | The provider | You |
| Who carries risk and compliance | The payment company | Mostly the provider | You, with the acquiring bank responsible to the card networks [V1] |
| How you earn | A referral fee or revenue share | The difference between what you pay the provider and what you charge customers, or a revenue share | The full margin between your cost and your price |
| Control over pricing and experience | Low | Medium to high | Highest |
| Work to launch | Lowest | Moderate | Highest |
What "embedded payments" means
Embedded payments means your customers sign up for payments, get paid and see their payouts inside your software, under your brand. They never leave for a separate payment company's site. For the platform, payments becomes a product line with its own revenue, on top of the software subscription.
Route 1: partner and refer
The platform signs a referral or reseller agreement and sends its customers to a payment company. Each customer applies for its own account with that company. The platform earns a referral fee or a share of the processing revenue.
This route is fast, and the platform carries almost no risk. The cost is control. The sign-up happens somewhere else, pricing is set by the payment company, and the platform sees little of the payments data.
Route 2: build on a provider's platform product
The platform embeds a provider's onboarding, checkout and payouts in its own product. The provider carries the regulated work: verifying each business, monitoring risk and moving the money. The platform owns the experience and usually the pricing.
Providers differ in how they charge and what they include. Two examples from the providers' own pages:
- Stripe Connect gives a platform two pricing options. Stripe can set and collect fees from the platform's users, or the platform can set its own pricing and pay Stripe $2 per monthly active account and 0.25% + 25¢ per payout sent [S2].
- Finix describes itself as an outsourced payment facilitator for software platforms and says it offers a path to becoming a payment facilitator [F1].
Questions to ask any provider on this route: Can we keep our current processor? Who verifies our customers? What do we earn per transaction? Who pays for chargebacks? How fast are payouts, and what do they cost? For a side-by-side list, read Stripe Connect alternatives.
Route 3: become a payment facilitator
A payment facilitator signs up businesses under its own agreement with an acquiring bank and pays them out itself. Visa describes a payment facilitator as a third party that acts for an acquirer, signs acceptance contracts with the businesses it sponsors, and receives and distributes their settlement funds. The acquirer has to register the payment facilitator with Visa after a risk and financial review, and stays responsible for what the payment facilitator and its sponsored businesses do [V1].
In practice that means the platform takes on underwriting, identity checks, fraud and chargeback monitoring, card-network compliance, data security and payout operations, with the staff to run them. In return it keeps the full margin and controls every part of the experience. This route suits very large platforms.
For how the four basic terms fit together, read payment processor vs payment gateway vs merchant account vs payment facilitator.
How to choose
- Volume. Small payment volume rarely repays the cost of becoming a payment facilitator.
- Risk appetite. Decide who should carry fraud losses, chargebacks and compliance. On route 3 it is you.
- Processor. If you already have a processor you want to keep, look for a provider that works with it.
- Revenue model. Compare a referral fee, a revenue share and a buy rate on the same sample of transactions. See embedded payments: buy rates vs sell rates.
- Checkout. Your payment revenue depends on buyers finishing the purchase. Ask what each option does for conversion at checkout.
Where Bolt fits
Bolt Connect sits on route 2. It gives a platform embedded checkout, seller onboarding and payouts in one integration.
- Processor choice. Bolt Connect runs on your own processor or on Bolt Payments. On your own processor there is no Bolt processing fee and no Bolt chargeback fee.
- Pricing. Bolt charges the platform a wholesale buy rate. The platform sets what its sellers pay, up to a ceiling Bolt sets, and keeps the difference.
- Identity checks. Bolt handles seller onboarding and identity checks on either processor.
- Payouts. Bolt's Transfers API, in beta, lets a platform pay sellers on its own schedule.
- Checkout. Buyers can check out in one click through a network of over 100 million shoppers, and sellers keep their customers' names, emails and other information.
- Add-ons. Total Fraud Protection and the Bolt Tokenizer are available as standalone add-ons, without Bolt checkout.
Bolt Payments is for US businesses. Bolt checkout on your own processor is global.
See Bolt for platforms, Bolt Connect, Bolt for payment processors and pricing, read Bolt Connect vs Stripe Connect, or talk to Bolt.
Sources
Read November 21, 2026:
- [V1] Visa, "Visa's Payment Facilitator Model: Expanding access to sellers" (February 21, 2024), usa.visa.com
- [S2] stripe.com/connect/pricing, Connect pricing
- [F1] finix.com/who-we-serve/software-platforms, "Embedded Payments Platform for SaaS and Software Platforms"
Bolt sources (read November 21, 2026): boltapp.com/platforms, boltapp.com/connect, boltapp.com/processors.
FAQ
How can a software platform add embedded payments?
In three ways: refer customers to a payment company, build payments into the product on top of a provider that carries the regulated work, or become a registered payment facilitator.
What is a payment facilitator?
A company that signs up businesses under its own agreement with an acquiring bank and distributes their funds. The acquiring bank registers it with the card networks and stays responsible for it.
Should my platform become a payment facilitator?
Only at very large volume, and only if you want to run underwriting, risk, compliance and payouts yourself. Most platforms build on a provider instead.
How do platforms make money from payments?
Through a referral fee, a revenue share, or the difference between a wholesale buy rate and the price the platform charges its customers.
Can a platform add embedded payments and keep its current processor?
Yes, with a provider that supports it. Bolt Connect runs on your own processor or on Bolt Payments.
Who verifies the businesses on my platform?
On the first two routes, the payment company or provider. With Bolt Connect, Bolt handles seller onboarding and identity checks. If you become a payment facilitator, you do.
Stripe and Connect are trademarks of Stripe, Inc. Visa and Finix are trademarks of their respective owners. Bolt is not affiliated with or endorsed by any of them.