SaaS Payment Processing Costs: What It Takes to Collect a Dollar of Revenue

by | Oct 9, 2026 | Business, Money

A B2B SaaS company with 1,000 self-serve customers paying 100 dollars a month moves 1.2 million dollars a year. Before any of it lands in the bank, it travels through a supply chain: an issuing bank, a card network, an acquirer, a billing engine, a tax engine, and a dunning process that decides how much arrives at all. Every link publishes a price. Almost none of those prices reach a board deck.

The numbers are not small. Work through the published rate cards most SaaS companies actually use and a monthly, card-billed customer costs roughly 4.4 percent of revenue to collect. The same customer on an annual bank debit costs about 1.6 percent. That gap is around 278 basis points of gross margin, available without touching the product, the price point or the sales motion. What follows works up that supply chain layer by layer, using only rates the suppliers publish. SaaS payment processing costs are an input cost structure, and input cost structures reward anyone who reads the invoice.

Why the cost of collection hides so well

Collection costs hide because they are netted. The processor deposits the money already short of its fee, so the expense never arrives as a bill anyone argues about. Hosting gets a cost function and a quarterly review; the 4 percent lost between the customer’s card and the company’s bank account gets one line in cost of revenue, if it gets one at all.

SaaS Capital’s annual survey of more than 1,000 private B2B SaaS companies found that bootstrapped companies with 3 million to 20 million dollars in ARR posted median revenue growth of 15 percent, median net revenue retention of 103 percent and median gross revenue retention of 91 percent in 2026, published 24 April 2026. Against a 15 percent median growth rate, 278 basis points of recovered gross margin is not rounding. It is permanent, it needs no customer to agree to it, and it scales with every dollar collected.

Layer one: the card rails

The largest single component of SaaS payment processing costs is usually interchange, the fee the acquirer pays the card issuer. The merchant cannot negotiate it, and the two largest networks publish it.

Visa’s United States interchange schedule, rates effective 18 April 2026, lists its Corporate and Purchasing programs explicitly. In the Purchasing and Corporate T and E column, Commercial Card Not Present is 2.70 percent plus 0.10 dollars, Non-Qualified is 2.95 percent plus 0.10 dollars, and Commercial Product 3 is 1.75 percent plus 0.10 dollars. Those three rates sit in the same table, in the same column. Top to bottom is 120 basis points on the identical card.

Mastercard publishes the same shape. Its United States merchant rate schedule, effective 17 April 2026, breaks the Small Business Credit table out by business level. For Business Level 1, Standard is 2.95 percent plus 0.10 dollars, Data Rate I is 2.65 percent plus 0.10 dollars and Data Rate II is 1.90 percent plus 0.10 dollars. One card, three prices, separated by what the merchant sends with the authorisation.

Bar chart of six published US commercial card interchange rates from Visa and Mastercard, April 2026
Source: Visa U.S.A. Interchange Reimbursement Fees, rates effective 18 April 2026 (Corporate and Purchasing table), and Mastercard U.S. Region Merchant Rates, effective 17 April 2026 (Small Business Credit, Business Level 1). Percentage components shown; each program also carries a fixed 0.10 dollar component.

Regulation sets a floor under part of this. The Federal Reserve’s Regulation II data page, last updated 19 December 2025, reports that for 2024 the average debit card interchange fee across all networks was 0.51 dollars on exempt transactions and 0.23 dollars on covered transactions, with an all-transaction average of 0.34 dollars. Split only by whether the issuer falls under the rule, the same card type costs the merchant roughly twice as much on one side of that line as the other. A meaningful share of what a SaaS company pays to accept money is set by rails and regulation, not service.

Layer two: what the acquirer adds

On top of interchange sits the acquirer’s margin, and here published rate cards diverge sharply in structure.

Stripe publishes a blended price: 2.9 percent plus 30 cents per successful transaction for domestic cards, an additional 0.5 percent for manually entered cards, an additional 1.5 percent for international cards, and an additional 1 percent if currency conversion is required. One number, easy to model and impossible to see through. Whatever the interchange on a given card, the merchant pays the same.

Adyen publishes the unbundled version. Its pricing page shows a fixed processing fee of 0.13 dollars per transaction, and for Visa and Mastercard globally the rate is listed as 0.13 dollars plus Interchange++ plus 0.60 percent, with interchange and scheme fees passed through at cost. The same page lists American Express at 0.13 dollars plus 3.3 percent plus 0.10 dollars in North America, and SEPA Direct Debit at 0.13 dollars plus 0.27 euros per transaction.

Both are honest prices answering different questions. A company whose customers pay on commercial cards qualifying for a low data rate is subsidising everyone else under a blended price. It is a procurement decision with a published answer on both sides, and most SaaS finance teams have never run it.

A third option is to buy the entire stack. Paddle, operating as merchant of record, publishes 5 percent plus 50 cents per checkout transaction, including tax registration and filing, fraud handling, chargebacks and buyer support. On a 1,200 dollar annual invoice that is 60.50 dollars against 35.10 dollars for a domestic card at Stripe’s published blended rate. The premium buys something real: for a company selling into dozens of tax jurisdictions, the alternative is a compliance function. The trade-off shifts with the revenue mix, which is why it belongs beside the sequencing questions in SaaS international expansion.

Bar chart comparing the cost of collecting a single 1,200 dollar annual SaaS invoice across four published payment rates
Author calculation applying four published rates to one 1,200 dollar charge: 35.10 dollars, 65.10 dollars, 60.50 dollars and 5.00 dollars. Rates from stripe.com/pricing and paddle.com/pricing as displayed on 9 October 2026. Stripe ACH Direct Debit is 0.8 percent with a 5.00 dollar cap, so the cap binds at this amount. Paddle’s rate is not like for like: as merchant of record it also covers tax registration and filing, fraud handling, chargebacks and buyer support.

Layer three: the billing and tax software

Subscription billing is the second meter. On the same published schedule, Stripe Billing is 0.7 percent of billing volume on its pay-as-you-go tier, and Stripe Tax Basic with a no-code integration is 0.5 percent per transaction where the merchant is registered to collect. Chargebee prices its billing product on monthly invoicing volume, showing 0.80 percent on the entry tier and 0.65 percent on the paid tier, with a stated breakeven at 66,000 dollars of monthly invoicing volume.

Individually these are not large numbers. Together they are 120 basis points on top of the card rate, charged on gross billings rather than net revenue. A billing stack costing 1.2 percent of revenue at 2 million dollars of ARR still costs 1.2 percent at 50 million unless somebody renegotiates it, and that rarely happens on schedule because nobody owns the line.

Layer four: the money that does not arrive

The final layer is leakage: the one with the least visibility and the most upside. Cards expire, get reissued after fraud, and get declined for reasons unrelated to intent to keep paying. Baremetrics published a benchmark drawn from 119 typical US B2B SaaS companies using its Recover product during May 2026. Across that sample, the companies recovered 1,236,764 dollars across 10,999 charges in that single month, at a median attempted recovery rate of 12.7 percent. The median is worth sitting with: half of these companies recovered less than 12.7 percent of the failed payments they attempted.

Disputes carry their own meter. Stripe’s published schedule lists a dispute received fee of 15.00 dollars for each dispute, charged whether or not the merchant wins. At a 29 dollar monthly price point, two disputes wipe out a month of revenue from a paying customer and then some. That is the caveat that rarely reaches pricing discussions: at low price points the fixed components of SaaS payment processing costs dominate the percentage components, and no rate negotiation fixes it.

The all-in number, on one customer

Put the published rates together on one customer paying 1,200 dollars a year.

Billed monthly on a domestic card through Stripe: twelve charges of 100 dollars at 2.9 percent plus 30 cents is 38.40 dollars, Billing at 0.7 percent adds 8.40 dollars, Tax Basic at 0.5 percent adds 6.00 dollars. Total 52.80 dollars, or 4.4 percent of revenue.

Billed annually by ACH Direct Debit: one charge at 0.8 percent would be 9.60 dollars, but the published 5.00 dollar cap binds, so it is 5.00 dollars. Billing adds the same 8.40 dollars and tax the same 6.00 dollars. Total 19.40 dollars, or about 1.62 percent.

The difference is roughly 278 basis points of gross margin on identical revenue from an identical customer. No discount, no feature, no repricing. The money was routed differently.

Bar chart showing the fixed-fee drag on 1,200 dollars of annual revenue falling as billing frequency falls from monthly to annual
Author calculation using Stripe’s published 30 cents per successful transaction, applied to 1,200 dollars of annual revenue collected in 12, 4, 2 or 1 charges. Rate as displayed on stripe.com/pricing on 9 October 2026.

Four levers, in order of size

Four moves change this number materially, and the order matters.

One: move the rail. Bank debit beats cards by an order of magnitude at normal SaaS invoice sizes. Stripe’s published ACH cap of 5.00 dollars means a 1,200 dollar annual invoice costs the same to collect as a 50,000 dollar one. Above roughly 625 dollars the cap is already binding, and the saving grows with contract value.

Two: change the frequency. The fixed per-transaction fee is charged per successful charge, not per dollar. Collecting 1,200 dollars in twelve charges costs 3.60 dollars in fixed fees; collecting it in one charge costs 30 cents. That is 0.3 percent of revenue versus 0.025 percent, and it arrives alongside the cash-flow benefit of annual prepayment. The pricing architecture that makes annual billing attractive is the same one covered in hybrid SaaS pricing.

Three: send the data. Both networks publish lower rates for transactions submitted with richer data. Mastercard’s Business Level 1 Data Rate II is 1.90 percent against a 2.95 percent Standard rate, a 105 basis point difference on the same card. Capturing this requires passing line-item detail through the authorisation, which is an integration task, not a negotiation.

Four: work the failures. A median attempted recovery rate of 12.7 percent across 119 US B2B SaaS companies in May 2026 means the median company leaves most of its recoverable failed revenue on the table. Retry logic, card account updater enrolment and dunning sequences are cheap relative to what they return.

Rate negotiation with the acquirer is deliberately not among those four. It is the move most teams reach for first and it shifts the smallest number, because the acquirer’s own margin is the thinnest slice of the stack.

What this changes about pricing design

Once collection cost is visible it starts to inform pricing rather than merely report it. Low-priced monthly plans carry the worst collection economics in the catalogue, because the fixed fee is constant and the price point is not. A 9 dollar monthly plan gives up 3.3 percent of its price to the 30 cent fixed fee alone. That argues for annual-only pricing at the entry tier, not against self-serve.

Published international surcharges argue for a currency strategy. Stripe’s rate card adds 1.5 percent for international cards and a further 1 percent when conversion is required, putting the all-in rate at 5.4 percent plus 30 cents, or 65.10 dollars on a 1,200 dollar invoice. Local acquiring is a margin decision, not just a conversion decision.

It also argues for treating billing architecture as something finance owns on a schedule. The move away from per-seat subscriptions, covered in the shift in SaaS pricing models, multiplies transaction counts. More invoices means more fixed fees: manageable if modelled, expensive if discovered.

SaaS payment processing costs are one of the few remaining margin levers that require no customer conversation, no product work and no repricing. The rates are published. The arithmetic is simple. The only hard part is that nobody has been assigned to do it.

Frequently asked questions

What percentage of revenue do SaaS companies typically lose to payment processing?

It depends on billing design far more than on the vendor. Using published rates, a customer paying 1,200 dollars a year in monthly instalments on a domestic card through Stripe costs 52.80 dollars to collect, combining card processing at 2.9 percent plus 30 cents, Billing at 0.7 percent and Tax Basic at 0.5 percent. That is 4.4 percent of revenue. Billed once a year by ACH Direct Debit, where the published 0.8 percent rate is capped at 5.00 dollars, the same customer costs 19.40 dollars, about 1.62 percent. That spread is wider than the spread between processors.

Is a merchant of record worth 5 percent?

Paddle publishes 5 percent plus 50 cents per checkout transaction, including tax registration, filing, fraud handling, chargebacks and buyer support. Against a domestic card at 2.9 percent plus 30 cents, the premium on a 1,200 dollar invoice is 25.40 dollars. Whether that is good value depends on how many tax jurisdictions the company sells into and what an internal compliance function would cost. In two countries it is usually expensive; in forty, often not.

What is Level 2 and Level 3 interchange data, and does it apply to SaaS?

Both networks publish reduced interchange for transactions submitted with detail beyond the basic authorisation. Mastercard’s Small Business Credit table shows Business Level 1 at 2.95 percent Standard, 2.65 percent at Data Rate I and 1.90 percent at Data Rate II. Visa’s Corporate and Purchasing table shows Commercial Product 3 at 1.75 percent against 2.70 percent for Commercial Card Not Present. It applies whenever customers pay on commercial, corporate or purchasing cards, common in B2B SaaS.

Why does billing frequency matter so much?

Because the fixed per-transaction fee does not scale with the amount. Stripe’s published 30 cents applies to each successful charge. Collecting 1,200 dollars across twelve monthly charges costs 3.60 dollars in fixed fees, or 0.3 percent of revenue; collecting the same amount in one annual charge costs 30 cents, or 0.025 percent. The percentage components are unchanged. Only the transaction count moved, and at small invoice sizes that count is the dominant term.

How much failed payment revenue is actually recoverable?

More than most teams assume. In a benchmark covering 119 typical US B2B SaaS companies using Baremetrics Recover during May 2026, those companies recovered 1,236,764 dollars across 10,999 charges in that month, at a median attempted recovery rate of 12.7 percent. That median means half the sample recovered less than 12.7 percent of what it attempted, which points at effort and tooling rather than customer intent. Card account updater enrolment and smarter retry timing are the usual first moves.

The short version

Revenue collection has a supply chain, every supplier in it publishes a price, and those prices say that how a SaaS company bills matters more than who it banks with. Routing a 1,200 dollar annual contract through a bank debit on one invoice instead of twelve card charges is worth about 278 basis points of gross margin on identical revenue. The work is reading the rate cards and assigning somebody to own the result.

Recent Posts

Where the Work Went After Agents Started Writing the Code

Where the Work Went After Agents Started Writing the Code

In September 2026, agents started 110 million pull requests on GitHub. That was more than 40% of the month’s total, against 17% in March, according to GitHub’s Octoverse 2026 report, which runs on GitHub’s own platform telemetry and, unless otherwise noted, covers public and private repositories for the Octoverse year ending 30 September 2026.

Explore Topics