PayFac is a business decision wearing a technology costume

Every software company that gets serious about payments eventually asks the same question: do we become a payment facilitator, or not? The conversation usually starts in engineering, because it sounds like a technology decision. It is not. It is a margin, risk, and ownership decision that happens to involve software.

I have built payment facilitation four different ways: platform-native on Stripe, global PayFac on Adyen, hybrid models on Worldpay, and the traditional route with direct BIN/ICA sponsorship. Each one was the right answer for that business and would have been the wrong answer for the others. That is the point most vendor decks skip.

The question underneath the question

Full PayFac means you own underwriting, boarding, settlement, chargebacks, and compliance. In exchange you keep the economics and control the merchant experience. Managed PayFac or PayFac-as-a-service hands most of that back to a provider, along with a meaningful slice of your margin. Staying a referral partner keeps you clean of risk and thin on revenue. The right position depends on three numbers: your payments volume today, your realistic attach rate, and the operating cost of the risk function you would have to build.

The honest math surprises people in both directions. Below a certain volume, full PayFac is a vanity project: you will spend more on compliance staff and sponsor requirements than the margin you capture. Above it, staying on someone else's paper quietly costs you millions a year and, worse, leaves your merchant relationships contractually owned by someone else.

What I look at first

When a platform asks me which way to go, I do not start with the technology. I start with the exit. Who is going to own this company in five years, and what will they pay for? Payments revenue with owned economics and portable merchant contracts re-rates a software multiple. Payments revenue that is really a referral fee on someone else's program does not. Work backward from that, and the architecture usually chooses itself.

The costume is technology. The body underneath is a P&L. Dress accordingly.