Payment Processing for SaaS Companies in the Bay Area

SaaS companies payment processing in the Bay Area almost always starts with Stripe, and for a seed-stage company in SoMa, Palo Alto, or Berkeley that is the right call. The question this post answers is what comes after: at what point a South Bay or San Francisco software company should look at a direct merchant account, what it gains, and how the card-not-present cost structure of subscription billing can be pushed down without a sales rep's help.

When the aggregator stops being cheap

A flat 2.9 percent plus 30 cents is a great deal at $20,000 a month. At $500,000 a month it is a large line item, and the composition of your volume starts to matter. Bay Area SaaS volume tends to skew toward:

• Commercial and corporate cards, which qualify for lower interchange with Level 2 and 3 data.
• Large annual invoices that would cost far less on ACH.
• International customers, where cross-border fees and currency conversion get expensive on a blended rate.

On a flat rate, none of that composition is visible or actionable. On interchange-plus, every transaction shows its actual interchange and the processor's fixed markup, and you can see what a Level 3-qualified corporate card costs versus a consumer rewards card. Our pass-through pricing page walks through the statement format. Companies that make the switch usually do it somewhere between $50,000 and $200,000 a month, or earlier if they bill mostly other businesses.

Level 2 and 3: the B2B discount hiding in your data

Commercial cards carry reduced interchange when the transaction includes tax amount and a customer reference (Level 2) or full line-item detail (Level 3). For a B2B SaaS company in Mountain View billing $3,000 monthly seats to corporate cards, that can be a meaningful reduction on a large share of volume. It requires a gateway that supports the data fields and a small integration to pass invoice details with each charge. Most aggregators do not expose this. Ask any processor you evaluate whether Level 3 is supported and whether it can be populated automatically from your billing system.

ACH for enterprise

Enterprise customers paying $30,000 annual contracts do not need to pay by card, and you do not want them to. ACH settles in 1-3 business days at a small flat cost. Cards settle in 1-2 business days, so the difference in timing is minor and the difference in cost is large. Offer ACH as the default on invoices above a threshold and cards as the fallback; most finance teams will take the bank transfer. If you serve customers who prefer to settle in stablecoins, stablecoin payments settle instantly to your wallet with no chargeback mechanism, which some international customers find simpler than wires.

Recurring billing rules: California and the networks

Two rulebooks apply to Bay Area subscription billing, and they overlap enough that one flow satisfies both. California's Automatic Renewal Law requires clear and conspicuous terms before the charge, affirmative consent, an acknowledgment with cancellation instructions, online cancellation for online signups, and notice before trial conversions and price changes. Visa and Mastercard's recurring and trial-billing rules require substantially the same things, plus specific descriptor conventions for the first charge after a trial. Build one compliant checkout and you have covered both. Confirm the current ARL details with counsel; the statute has been amended more than once.

A note for usage-based and seat-based pricing: variable-amount recurring charges are allowed, but the customer needs to have agreed to the pricing formula, and a large unexpected charge is a dispute waiting to happen. Send a heads-up when a bill will be materially larger than the last.

Network tokens and authorization rates

For a company with tens of thousands of cards on file, authorization rate is revenue. Network tokens, issued by Visa and Mastercard and tied to the card account rather than the card number, survive reissuance and typically authorize at a higher rate than raw card numbers. Combined with account updater and decline-code-aware retries, they cut involuntary churn substantially. The difference between a network token and a plain vault token is covered on our tokenization page. Ask any processor whether network tokens are on by default and whether there is a cost per token.

Underwriting a Bay Area SaaS company

Most software companies are easy approvals. The exceptions worth flagging on the application: significant annual prepay (exposure on the unused term), customers in high-risk verticals, and any model where you move money on behalf of users, which is a marketplace or payfac conversation rather than a merchant account. Underwriters will also look at refund policy and churn, so have twelve months of data ready. A company coming off an aggregator shutdown should read Why Did Stripe or PayPal Shut Down My Account? before applying, because the explanation you give matters.

PCI and engineering time

Your engineers' time is expensive. Hosted fields keep card data off your servers, which keeps you on a short self-assessment questionnaire instead of a full audit, and a token vault means your database never stores anything a breach could expose. Both also reduce your CCPA/CPRA surface area, which matters for any company holding data on California consumers. Finance will want settlement data with subscription IDs attached; Flux pushes transactions into QuickBooks one-way, so accounting reflects payments without the books being altered from the payments side.

The Bay Area has more SaaS companies than any market on earth, and most of them are overpaying for card processing by a little and for B2B card processing by a lot. Interchange-plus, Level 3, ACH for enterprise, and network tokens are the four changes that move the number.