Accept, Secure, Manage, Grow: a framework for auditing your payments stack

Ask a SaaS operator how payments are going and you'll usually hear one number: the revenue share check. It tells you what payments paid you last month. It says nothing about what they cost you in failed checkouts, support tickets and merchants who process somewhere else, or about the revenue line you never built.

We split a payments stack into four stages: Accept, Secure, Manage and Grow. It's how we organize our own product, and it works as well on anyone else's. Below is what good looks like at each stage, with one test that tells you where you stand.

Accept: can your merchants take every payment their customers want to make?

Most audits stop at "we support cards." Go further and list the ways your merchants' customers actually pay, in person, online, by invoice, through a wallet or in another currency, then check each against your setup.

In a healthy stack a merchant takes a payment at the counter, on the web and over the phone without leaving your software. Approval rates are visible and tracked month to month. Local methods customers expect, like Interac in Canada, sit inside the same integration instead of with a second provider.

The test: count the merchants running a separate terminal or gateway beside your product. Every payment that goes around your software is revenue and data you never see.

Secure: who carries the risk when something goes wrong?

Security reviews tend to stall at the compliance badge. PCI-DSS Level 1 is the bar for anyone processing at scale, and it matters. It just doesn't tell you who does the work when a payment goes bad.

Find out who handles underwriting and onboarding checks, who manages disputes and how fast a merchant hears about one, and what your own PCI scope looks like. A well-built integration keeps raw card data off your systems entirely.

The healthy version is a split of responsibilities written into the contract: your team owns the software, your partner owns the payments risk. The test is simple. Ask who owns a chargeback. If nobody can answer, you do.

Manage: can your merchants run their money from inside your product?

Once a payment clears, the merchant's real work starts. Deposits need reconciling, batches need matching, the accountant wants statements. When all of that lives in a separate portal, merchants think of payments as someone else's product, and sooner or later they compare it to someone else's price.

Good reporting lives where your merchants already work. Transactions, deposits, batches and statements show up in real time and export cleanly, and your support team sees what the merchant sees, so a "where's my money" ticket takes minutes instead of a call to the processor.

The test: pull last month's support queue and count the payments questions your team couldn't answer without escalating. That number is how much this stage is costing you.

Grow: is payments a revenue line or a pass-through?

Most software companies skip this stage, and it's the one that changes the economics. Payments can stay a cost you pass through, or they can become a line on your P&L that grows with your merchants.

Three things decide which. Your economics, meaning the share of processing margin you keep and whether you set pricing to your merchants. Your attach rate, meaning the share of merchants who actually process through you, and why the others don't. And what you can offer on top, such as financing, faster payouts or better reporting, each of which adds revenue per merchant without a new customer.

The test: can you state your attach rate from memory? Teams that can usually have a plan to raise it. Teams that can't usually don't.

Running the audit

Take the stages in order, because acceptance problems hide everything after them. You can't secure, manage or grow payments that never run through you. Mark each stage solid, shaky or missing, and write down the one fix that would move it. Most teams find their weakest stage inside an hour, and it's rarely the one they expected.

For a quicker read, the Payments Health Score at valpay.com/payments-health-score covers the same ground in about two minutes. It's free.