Payments for MSPs: Per-Seat Billing, ACH vs. Card Math, and the Processor Tiers

The short version, peer to peer: an MSP is a recurring-revenue business with a seat-count problem — $150/seat × 500 seats is $75,000 a month, and the card-vs-ACH decision on that volume is a $25,000-a-year decision. The PSA already does the billing; the question is what rails it runs on and who eats the fee. Here is the fee table at MSP ticket sizes, the dunning discipline that protects MRR, and the honest processor tiers. Rates checked October 2026. Also see IT Providers, AI for MSPs, and Tech for IT Providers.

The fee table: card vs. ACH on $75,000/month in MRR

500 seats × $150, rates checked October 2026:

• Cards via Stripe (2.9% + $0.30): ~$2,175/month in fees — $26,100/year. Per seat: $4.35/month of your $150.
• Cards via Square (2.9% + $0.30): same ~$2,175/month — plus Square is not built for B2B recurring at this scale.
• ACH via Stripe (0.8% capped at $5 per transaction): on per-client invoices (say 40 clients averaging $1,875): ~$200/month — $2,400/year.
• PSA-native payments (ConnectWise, Syncro, SuperOps payment integrations): typically ~2.99% + $0.30 on cards — the premium buys invoice-to-ledger sync inside the PSA.
• Interchange-plus (Chase/Fiserv/Global Payments/Worldpay): ~1.8–2.2% effective on B2B cards — ~$1,400–$1,650/month. Worth negotiating at this volume if clients insist on cards.

The delta between card-default and ACH-default billing is over $23,000 a year at this scale. The MSP payments strategy in one line: ACH default on every managed-services agreement; cards as the client-paid convenience option. The clients who want points can have them — at their expense.

The workflow checklist (you know this list — enforce it)

• Seat-count true-ups monthly — the PSA's agreement count vs. actual deployed seats, reconciled every month. The 3–5% MRR drift lives here; automation (or the voice workflow from the AI guide) kills it.
• Dunning with teeth — failed payment day 1, retry day 3, notice day 5, service-impact warning per the MSA. Stripe Billing and most PSA payment modules handle the mechanics; the policy is yours.
• Project milestone billing separate from MRR — project invoices on the SOW schedule, never blended into the seat invoice. Blended invoices hide project margin.
• Hardware pass-through — client hardware billed at cost-plus with the margin explicit. The processor does not care; your P&L does.
• Multi-entity client billing — the client's three entities, three invoices, one payment. Finix's public docs on invoicing and split mechanics are a useful reference when the PSA's native tools strain.
• Annual prepay incentives — 12 months for the price of 11, paid by ACH. The discount costs less than the card fees it replaces, and the cash lands in January.

The honest processor tiers

Tier 1 — PSA-native payments: the default. You pay ~2.99% for invoice-to-ledger sync inside the system your techs live in. Worth it for the reconciliation alone — but route it to ACH where the module allows.

Tier 2 — Stripe: the best generic rails. Use it when the PSA's payments cannot do what you need (custom dunning, multi-entity). ACH pricing is the reason it is here.

Tier 3 — Interchange-plus (Chase/Fiserv/Global Payments/Worldpay): negotiate it when card volume justifies it (~$50k+/month on cards). Below that, the account overhead is not worth the basis points.

Not on the list — Square, Adyen: Square is not a B2B recurring tool; Adyen is enterprise rails for enterprise volume. Neither belongs in an MSP's billing stack.

The unpopular opinion: most MSPs should spend less time choosing a processor and more time enforcing ACH-default in the MSA. The contract term is worth more than the rate negotiation. For the voice-driven front end — speak the seat change, update the billing — ClaroPro keeps the count honest so the MRR is real.

Hardware-as-a-service: the financing conversation worth having

The hardware refresh is the MSP's awkward sale: the client needs $40,000 of laptops and servers, does not want the capex hit, and the MSP does not want to be the bank. Hardware-as-a-service (HaaS) solves it — the hardware bundled into the monthly seat rate over 36 months — and the payments structure is the product.

The honest mechanics: you finance the hardware (through a leasing partner like GreatAmerica or TAMCO, or your own balance sheet if you are large enough), the client pays monthly, and the agreement ties the hardware term to the MSA term so the refresh and the renewal arrive together. The margin is in the spread and in the refresh cycle you control — no more "we'll replace them when they die" turning into a seven-year-old fleet. The risk is the early termination: the MSA must make the remaining hardware payments survive cancellation, or you own $30,000 of used laptops. Price the risk into the rate, document it in the agreement, and HaaS becomes the stickiest revenue in the business — the client cannot leave without buying out the hardware, which is exactly the point.

The MSA pricing conversation: per-seat, per-device, and tiered

The MSA pricing model is the business model, and the three options price different realities. Per-seat ($125–$200/user/month) is the standard — simple, predictable, aligned with the client's headcount. Per-device ($25–$75/device/month) fits device-heavy clients (warehouses, retail) where users share endpoints. Tiered (bronze/silver/gold) productizes the upsell — the security stack, the vCIO hours, the after-hours SLA each live in a tier the client climbs.

The honest guidance: per-seat for the standard office client, per-device where the device count dwarfs the user count, tiered when you have a real vCIO and security story to sell. Whatever the model, the agreement must define the count mechanics — what counts as a seat, when adds/removes bill, the true-up cadence — because the pricing model is only as good as its measurement. And price the security stack as a separate line: the clients who see the security cost buy more of it, and the MSPs who bury it eat it.

FAQ

Should MSPs bill by credit card or ACH? ACH by default — the $23,000+/year delta at 500 seats is the whole answer. Cards as the client-paid convenience option.

What about the PSA's native payments? Use them for the ledger sync; configure ACH wherever the module allows. The ~2.99% card rate inside the PSA is a convenience tax — pay it only where cards are genuinely needed.

How do I stop seat-count drift? Monthly true-up: PSA agreement count vs. deployed seats, reconciled and billed. The voice workflow in the AI guide turns "added 8 seats" into a billing event at the tech's desk.

When does interchange-plus make sense? Past ~$50k/month in card volume. Below that, ACH-default beats any negotiated card rate.

Should we finance hardware ourselves? Below real scale, no — use a leasing partner (GreatAmerica, TAMCO). Your balance sheet is not a bank until it is.

What happens to HaaS on early termination? The agreement must keep the hardware payments alive past cancellation — buyout or continued payments. Document it before the first deal, not during the first dispute.

Per-seat or per-device? Per-seat for office clients; per-device where devices dwarf users. The count mechanics in the agreement matter more than the model choice.

The move: 1) ACH-default in every MSA renewal this quarter. 2) Monthly seat-count true-ups — no exceptions. 3) Project milestones billed on the SOW schedule, separate from MRR. The MSP that bills what it deploys, on rails that cost $5 instead of $2,175, has already found the margin. For the PSA decision underneath, read Tech for IT Providers; for the rails, Finix-grade ACH is the peer-reviewed answer.