How to Pick Payments Infrastructure for Vertical Software

Who this is for

The founder, COO, or head of fintech at a vertical software company that already has merchants or sellers in the product and wants to take a rate on their card volume. You are picking infrastructure, not shopping a consumer checkout plugin for one store.

This page is not for a single-merchant gateway decision. It is not for deposits, spend cards, or working capital. Those jobs live on banking, cards, and lending. It is also not a ranked table. The payments list is editorial. Order is not a score you can buy.

The decision tree (Connect-style platform payments vs PayFac-as-a-service vs becoming the PayFac)

Three jobs get sold as “embedded payments.” They are not the same business. Name the job before you name a vendor.

Connect-style platform payments. The licensed processor (or its registered facilitator) stays on the acquiring program. You onboard connected accounts, embed checkout and payouts, and take an application fee, partner fee, or split on each charge. You do not set interchange. You do not own merchant processing terms. Time-to-live can be a public integration and a fee field. On this directory that shape is Stripe Connect (the default start when you want payments revenue without becoming a PayFac), plus global or marketplace cousins such as Adyen for Platforms, Checkout.com Integrated Platforms, PayPal Complete Payments Platform, and Nuvei for Platforms. What you get: a documented take and someone else’s license. What you do not get: residual economics you own, a published interchange-plus buy rate you mark up at will, or a white-label acquiring program.

PayFac-as-a-service. Another party is the registered payment facilitator. You embed acceptance, usually set the merchant sell price, and keep the merchant relationship. They underwrite sub-merchants, hold the acquiring program, and stay on the processing terms. The usual buy-rate shape is interchange-plus you mark up, or an order-form buy rate you are not allowed to sell below. Production is almost always a sales conversation, not a self-serve live key. On this directory that shape includes Rainforest (published IC+, they stay on merchant terms, not a path to become the PayFac), JustiFi (they are the registered PayFac; you set rates), Payabli, Tilled, and Stax Connect. Some stacks also sell a later path to take the license on the same API: Finix, Infinicept (Launchpay holds registration now), Worldpay for Platforms, and Payroc (referral through managed PayFac). A path is a product choice. It is not residuals today, and it is not a reason to skip the “who is registered” question.

Becoming the PayFac. Your company (or a named affiliate) is the registered facilitator on a sponsoring acquirer. You underwrite sub-merchants, you take more residual economics, and you take more liability when a merchant goes bad. Card-network registration runs through that acquirer. It is not a dashboard toggle and not a larger application fee. Most teams on this directory should not start here. Start here only if owning underwriting, merchant terms, and the book is the actual job, and you can name the sponsor and the ops that will run KYC, monitoring, and loss. If marketing calls you a PayFac and the contract says they hold registration, you bought PayFac-as-a-service. Name it that way.

Not this tree. Spreedly and Primer are payments orchestration and vaulting. They are not the processor of record and not a PayFac. Dwolla is bank-rail money movement, not card acquiring as the primary job. Astra and TabaPay are accept-and-payout or push-to-card programs. Moov sits across accounts, wallets, ACH, and card acceptance; read that listing as a rail bundle, not as a substitute for the three jobs above. If the job is one of those, stop using this page as the pick.

Volume, license, time-to-live, residual economics

There is no public volume number on this directory that tells you when to become a PayFac. Vendors will quote program minimums in a sales room. Those are commercial, they change, and this page will not invent a threshold so a pitch deck can look quantitative.

License is the first honest question. Who is registered with the networks? Who underwrites the sub-merchant? Who is named on the merchant agreement? Connect-style answers: the processor. PayFac-as-a-service answers: the vendor (or its named facilitator). Becoming the PayFac answers: you, after an acquirer registers you. If you cannot get a one-sentence answer, you do not have a pick yet.

Time-to-live is not a feature comparison. Connect-style can be a public integration and, on at least one listing, a self-serve application-fee start. PayFac-as-a-service is a sales-led program: sandbox and docs may be public; live money waits on an order form, KYB, and their underwriting of your merchants. Becoming the PayFac is a registration and an operating company. This page does not print a month count. If a vendor will not say whether production keys wait on sales, believe the listing that already said sales-led.

Residual economics are the leftover processing spread over time, not a one-time SaaS fee and not an application fee on someone else’s rate card. An application fee ships this quarter and usually dies when you leave the stack or they change pricing. A published interchange-plus buy rate lets you explain the cost stack. It does not assign the merchant book to you. A documented path to take the license is how some teams try to own residuals later. Ask whether the spread is assigned to you, whether it survives a processor or bank change, whether there is a buyout, and who the merchant agreement names. If a listing says residual economics you own are not the fit, believe it.

Start here / Skip if

Start with Connect-style if you want payments revenue without standing up underwriting, you can live with the processor’s rate card, and time-to-live matters more than setting merchant price or owning the book. Read Stripe Connect first. If the merchants or the geography are a marketplace or a global acquiring conversation, read the platform listings next to it. That is a fit check, not a rank.

Start with PayFac-as-a-service if you will set the merchant sell price, stay the software brand your merchants already trust, and accept a sales conversation while someone else stays registered. If you need the buy rate visible, prefer listings that publish interchange-plus or say the plus lives on an order form. If you might take the license later, restrict the short list to stacks that document a same-API path, and still underwrite the “who is registered today” question. If you will never take the license, do not pay extra for a path you will not walk.

Do not start by becoming the PayFac. Skip that job if you cannot name a sponsoring acquirer, you do not intend to run underwriting and monitoring, or you are using “PayFac” as a synonym for “we take a rate.” Taking a rate is the Connect-style or PFaaS job.

Skip this page if the job is a single storefront, bank rails only, a PCI vault you will port across processors, issuing spend cards, or deposit accounts. Those are other tables.

Live payments peers. Editorial fit only. Not a rank, not a buy order.

Stripe Connect: Connect-style default start. Application fees. Stripe keeps the license and the rate card.
Rainforest: PFaaS with a published interchange-plus buy rate. You set sell price. Not a path to become the PayFac.
Finix: PFaaS now, same API if you later take the license. The path is not residuals on day one.
JustiFi: They stay the registered PayFac. You set merchant rates and keep the relationship. Sales-led.
Infinicept: White-labeled PFaaS with Launchpay holding registration, and a same-stack path to registered PayFac later.
Worldpay for Platforms: Worldpay acquiring and PFaaS, with a later PayFac developer path. Not a license you own the day you sign.
Adyen for Platforms: Global acquiring and split payouts, sales-led. A Connect-style cousin, not a self-serve application-fee start.
Spreedly: Orchestration and a PCI vault you control. Not the processor of record. Not this decision tree.

Payment facilitator: Who is actually registered.
PayFac-as-a-service: Renting that model so the software company is not the registered party on day one.
Application fee: The Connect-style take. A cut on someone else’s charge, not a residual book.
Interchange-plus: The buy-rate shape. Visible plus is not ownership.
Residuals: Leftover economics over time, and whether they survive if you leave.

FAQ

Do I need to become a PayFac to take a rate on merchant volume?

No. That is the point of this page. Most vertical software companies embed payments and take a rate while another party remains the registered facilitator or the licensed processor. Becoming the PayFac is a later ownership decision.

If I take an application fee, do I own residuals?

Usually no. An application fee is a platform cut while the processor keeps the license and the rate card. Residuals are an ongoing claim on the spread as merchants process, including what happens if you change stacks. Read the contract. Do not equate a fee field in an API with a residual book.

A vendor has a path to become the PayFac. Should I start there?

Only if you actually intend to take the license, and only after you are honest about who is registered today. A same-stack path is useful when you want one integration now and ownership later. It is a bad reason to skip Connect-style if you just need a rate this quarter, and a bad reason to ignore a simpler PFaaS listing that will never make you the PayFac (and is clearer about that).

Is payments orchestration the same pick as taking a rate?

No. Orchestration and vaulting (multi-processor routing, portable tokens) are how you avoid lock-in or raise auth rates. They do not make you a PayFac and they do not, by themselves, put an application fee in your bank account. If that is the job, read those listings as a different cluster.

How much volume do I need before I become a PayFac?

This directory does not publish a number. There is no honest public threshold that turns a software company into a registered facilitator. Ask the acquirer or the vendor what their program requires, treat the answer as commercial, and do not start from a blog statistic. If you cannot get the license question answered in one sentence, you are not ready for the volume question.

How to pick payments for vertical software