For years, the sixteen digit card number was the transaction. It was the thing you stored, the thing you charged, the thing you protected. If you ran a software platform that touched payments, your whole world quietly organized itself around keeping that number safe and keeping it current. That number
Most software companies meet PCI scope at the worst possible moment. A prospect’s security team sends a questionnaire. An acquirer asks for an Attestation of Compliance. A merchant forwards a notice from their bank and wants to know what it means. The scramble that follows is rarely a sign that
Every ISV is already running a second business inside the first one. Customers use the software to run their operations, and those operations move money. Invoices get paid. Memberships renew. Bookings get charged. Every one of those transactions generates revenue for someone. The only open question is whether any of
Some of the most important changes in payments never make headlines. They happen underneath the checkout page, inside the authorization flow, where most software companies never look. Network tokens are one of those changes. Over the past few years, the card networks have quietly rebuilt how card credentials move through
Every Constellation Software operating company that wanted to embed payments has faced the same decision. Build the infrastructure yourself, with all the compliance, underwriting, and risk work that comes with it. Or bolt on something generic that was never designed for how vertical market software actually operates. That decision is
Stripe is a remarkable piece of engineering. For a startup taking its first online payment, or a horizontal app serving customers across every industry at once, it is hard to beat. That is not the question worth asking. The question for a vertical SaaS company or an ISV is narrower
Embedding payments is one of the highest-leverage moves a vertical SaaS company can make. The hard part is timing. Here is how to tell where you stand. Done at the right moment, embedding payments turns a cost center into a revenue line and makes your product meaningfully harder to leave.
For most businesses, a payment gateway is something you choose once and rarely think about again. For an independent software vendor, it is the opposite. The gateway you select becomes infrastructure that your product, your merchants, and a real revenue line all sit on top of. Choose well and payments
Walk into any payments conference and you will hear “partnership” used a thousand times. Sales decks lead with it. Press releases announce it. RFP responses promise it. Yet most ISVs and software companies will tell you, off the record, that their payments partnership feels more like a vendor relationship dressed
Pricing model selection is one of the most consequential decisions an ISV makes about its payment stack, and one of the least examined. Most operating companies default to flat rate processing because the math is simple and the contracts read clean. The cost of that default, for any business with
