We Buy Payfacs Get an offer

Payfac as a service: what you own

Payfac-as-a-service, or a managed payfac, is a setup where a provider runs the payment facilitator role for your software platform. The provider often holds the sponsor bank contract, card-brand registration and settlement flow. What you own is usually your software, customer relationships, data and a contractual revenue share. Whether a buyer can take those over depends on your platform agreement.

Request an offer

Published November 20, 2026 · 6 min read

A countertop card payment terminal asking the customer to insert, swipe or tap

What payfac-as-a-service means for a seller

Payfac-as-a-service, or a managed payfac, is a setup where a provider runs the payment facilitator role for your software platform. The provider often holds the sponsor bank contract, the card-brand registration and the settlement flow, while you own the product and the customer relationship.

Visa defines a payment facilitator as an entity that contracts with an acquirer to deposit transactions, receive settlement, or contract with the acquirer on behalf of a sponsored merchant. Visa also says an entity that either signs sellers on the acquirer's behalf or receives settlement for them counts as a payfac, even if it does only one of the two. Each payfac is registered with Visa by its sponsoring acquirer, and the acquirer must obtain a Payment Facilitator identifier that travels with every transaction. So "who is the payfac here?" has a factual answer: whoever holds that acquirer contract and that identifier.

One vendor guide describes software platforms moving from an owned payfac to a managed or payfac-as-a-service model because underwriting, fraud management, reserves and compliance are costly to run in house. That is a reasonable business choice. It changes what you can sell, not whether you have something worth selling. If you want the basics first, read what a payfac is.

Who holds the registration and the settlement

Three facts in your paperwork decide it: who signed the acquirer agreement, whose payfac identifier is on your transactions, and who receives settlement before your merchants are paid. Whoever holds those carries the payfac duties.

QuestionIf you are the registered payfacIf your provider is the payfac
Who signed the acquirer or sponsor bank agreement?YouThe provider
Whose Visa registration and PF identifier are used?Yours, registered through your sponsoring acquirerThe provider's, registered through its acquirer
Who is liable for sub-merchant disputes and transactions?You, under the payfac agreement Visa requiresThe provider toward its acquirer; your platform agreement sets what passes to you
Who receives and directs settlement?You, unless the acquirer chooses to settle merchants directlyThe provider or its acquirer
Who underwrites sub-merchants (KYC/KYB)?You, under Visa's due-diligence ruleThe provider, or you under its standards, per contract
Who sets and holds reserves?You, on your sub-merchants; your acquirer may also hold one on you, per contractSet by your platform agreement

The line between those two columns is drawn by what you do, not by the product name. Visa's payfac agreement makes the payfac liable for its sponsored merchants' acts and financially liable for each transaction, so the role matters. If your company signs merchants on an acquirer's behalf or receives their settlement funds, Visa's definition may reach you whatever the provider calls the service. A buyer will want your counsel's view on which side of the line you sit.

A long row of supermarket checkouts with cashiers at work, 1970s
Every merchant in a portfolio is a till like these.

What you actually own on a managed payfac

If the provider is the registered payfac, the registration and the acquirer contract are its assets, not yours. Your value sits in four other places, and your contracts decide how much of each you own.

  • Software and IP. In payments M&A, technology is often a key asset and value driver. A buyer will check that it is explainable, secure and scalable, and open-source license issues can become closing conditions.
  • The merchant relationship. Check who is the counterparty on each sub-merchant agreement. If it is the provider, your merchants are its sponsored merchants, and your claim is to the software subscription and the revenue share, not to the merchant contract itself.
  • The revenue share. Your payments income is a contractual right under the platform agreement. Read whether it continues after termination, whether it can be assigned, and whether it survives a change of control. ISO agents ask the same question when they check whether their residuals are vested, or "paid forever".
  • Data. Merchant-level volume, dispute and attrition data, and your right to keep it. One payments software vendor puts it plainly: the deeper the analytics and proof a seller can offer, the higher the multiple a portfolio is likely to command.

How the platform agreement decides portability

Your platform agreement is the first document a buyer reads. Its assignment, change-of-control, termination and data clauses decide whether your book can move to a buyer, stay where it is under new ownership, or neither.

Courts have read payments contracts on their plain language. One payments law firm points to Process America, Inc. v. Cynergy Holdings, LLC (2d Cir. 2016), where portfolio ownership, post-termination residual rights, rights of first refusal and non-solicits were enforced as written. Read your agreement the way a buyer will.

ClauseWhat to look forWhy a buyer cares
AssignmentCan you assign the agreement, and with whose consent?An asset sale needs each contract assigned explicitly
Change of controlDoes a sale of your company need the provider's consent or let it terminate?Even a stock sale can need sign-off
Termination and migrationWhat happens to merchants, data and payouts if you leave?Decides whether a buyer can move the book to its own payfac
Revenue share survivalDoes your share continue after termination, and on what conditions?Decides whether the income is a durable asset
Non-solicit and exclusivityWho may approach the merchants, and for how long?Protects or limits the buyer after closing
Reserves and lossesWho funds losses, and what is held back on exit?Shapes the holdback in the purchase agreement

Adam Atlas, writing in The Green Sheet about ISO portfolio sales, made the buyer's position clear: a buyer will not release the purchase price without knowing beforehand that, after closing, the residuals will be paid to the buyer instead of the seller. The same logic applies to a platform revenue share. If your provider has to sign something for that to happen, that signature is part of your timetable. Our post on sponsor bank consent and change of control covers the same issue one level up.

What is sellable, and how buyers price it

A managed-payfac business can usually be sold in one of three ways: as a company, as a set of assets, or as a book a buyer moves to its own payfac. Which ones are open to you depends on the clauses above.

  1. Sale of the company. The platform agreement stays with your company, so the change-of-control clause is the gate.
  2. Asset sale. The buyer takes the software, the contracts and the revenue share, and each contract needs an explicit assignment. Buyers of payments companies often prefer asset deals because they control which liabilities come across. Tax effects differ by structure, so check with your CPA.
  3. Migration. A buyer that runs its own payfac moves your merchants onto it. That needs portability rights, merchant consent where contracts require it, and a plan to keep merchants. As one industry article put it, what matters most is continuity, so merchants have no reason to switch.

Price follows durability. One advisor writing in The Green Sheet called attrition, measured by both account count and revenue, the single most important variable in residual valuation, and the same logic applies to a platform revenue share. Concentration, dispute history and contract rights also move the number. A revenue share that ends when the platform agreement ends is worth less than one that survives it. Our payfac valuation guide explains how buyers weigh these.

What a seller should do next

Pull your platform agreement and answer the questions in the first table before you speak to any buyer. Then gather the data that proves the income.

That means two to three years of revenue-share statements by merchant, merchant counts by month, dispute and refund history, and the agreement itself. Have your payments lawyer confirm who the registered payfac is and what the change-of-control and termination clauses allow. This post is not legal or tax advice. If you do hold your own payfac registration, our page on selling a payfac covers that sale instead.

When you are ready, use the offer request form with ranges, not documents. We look at managed-payfac businesses on their own contracts and data, tell you which structure we think fits, and put an indicative offer in writing.

Home / Guides / Payfac as a service: what you own

Questions sellers ask

Can I sell my business if I use payfac-as-a-service? In many cases, yes. You are selling a software company with a payments revenue stream rather than a registered payfac. What a buyer can take over depends on your platform agreement: whether it can be assigned, whether a change of control needs the provider's consent, and whether your revenue share survives termination. Have your lawyer read those clauses first.

Do I own my sub-merchants on a managed payfac? Check who signs the sub-merchant agreement. If the provider is the counterparty, the merchants are its sponsored merchants under its acquirer, and you own the software relationship and your contractual revenue share. If your company signs merchants or receives their settlement, you may be acting as a payfac yourself, which your counsel should confirm.

Does a payfac registration transfer when a managed-payfac business is sold? If the provider is the registered payfac, the registration stays with the provider and does not form part of your sale. Visa registers payfacs through their sponsoring acquirer, and that registration is specific to each acquirer. A buyer moving your merchants to its own payfac works under its own registration.

Can a buyer move my merchants off the payfac-as-a-service provider? Only if your contracts allow it. Look for termination and migration terms, data rights, non-solicits and exclusivity in the platform agreement, and assignment terms in the merchant contracts. Without portability, a buyer usually buys the company or the assets and keeps the provider in place.

How is a managed-payfac business valued? On the durability of its income: attrition by merchant count and revenue, concentration, dispute history, and whether the revenue share survives termination or a sale. The software is valued as well. There is no single multiple. See our payfac valuation guide.

Read next

Ask for an offer

Ranges are fine. No merchant names, no statements, nothing you would not put in a first email.