Payment Processing for SaaS Companies in San Francisco

For SaaS companies payment processing in San Francisco is usually an afterthought until the first real annual contract, the first failed renewal cohort, or the first month where chargebacks show up on a dashboard someone actually reads. Whether you are three people in a Mission Street sublet or a Series B team in SoMa, the mechanics are the same: an acquiring bank is extending you credit on every future obligation you sell, and it prices that credit accordingly.

Why software is underwritten at all

Founders are often surprised that a business with no inventory and no shipping needs underwriting. The reason is delivery risk. When a customer pays for twelve months up front, the card networks treat the unfulfilled portion as a liability. If you shut down in month four, the cardholder can dispute the remaining eight months and the acquirer eats it. That is why an underwriter will ask about your runway, refund policy, how far in advance you bill and what share of revenue is annual prepay versus monthly.

A typical SF SaaS file lands in a low or moderate risk tier: MCC 5734 or 7372, monthly billing, B2B customers, low chargeback history. Files that move toward high-risk include consumer-facing subscriptions with free trials, anything with a coaching or "make money" angle, and companies with heavy international volume.

Recurring billing and the Automatic Renewal Law

California's Automatic Renewal Law requires clear and conspicuous disclosure of renewal terms, affirmative consent before the first charge, an acknowledgment the customer can keep, and a cancellation path that is at least as easy as signup. If you sell online, the customer has to be able to cancel online. Visa and Mastercard layered similar rules on free trials and negative-option billing: a reminder before a trial converts, a descriptor that identifies you clearly, and a receipt at each renewal.

These rules are worth following even if you sell exclusively B2B, because the enforcement mechanism that actually bites is the chargeback. A customer who cannot find the cancel button disputes the charge, and enough of those push you toward the 0.9 percent to 1 percent ratios where network monitoring programs start. The mechanics are covered in more depth in Subscription Billing Without Triggering Chargebacks.

Annual contracts: cards versus ACH

A $30,000 annual invoice on a corporate card costs you interchange on the full amount. Commercial and corporate cards carry some of the highest interchange categories, so the effective rate on that one invoice can exceed what you pay on a year of $99 monthly charges. Most SF SaaS companies past seed stage push annual contracts to ACH debit, which settles in 1-3 business days and costs a flat or capped fee instead of a percentage. Cards stay for self-serve monthly plans, where the card-on-file convenience matters and the ticket is small.

• Monthly self-serve: cards, tokenized, with account updater so expired cards renew.
• Annual mid-market: ACH by default, card accepted with a documented surcharge or dual-price if you choose to pass through cost, noting that California's SB 478 requires any mandatory fee to be in the advertised price.
• Enterprise: invoice and wire or ACH, with a payment link for finance teams who want to pay by card anyway.

Tokenization, hosted fields and your PCI scope

Engineering teams here tend to build their own billing flows. That is fine as long as card data never touches your servers. Using hosted fields keeps the card input inside the processor's iframe while your product controls the look, which keeps you eligible for the shorter self-assessment questionnaire instead of a full audit. Tokens returned from the vault are what you store and what you charge on renewal. If you ever migrate processors, ask up front whether tokens are portable; some vendors treat the vault as a lock-in.

International customers and currency

A large share of SF SaaS revenue comes from outside the US. Cross-border interchange and currency conversion add real cost, and issuer declines on foreign cards are higher. Practical steps: present prices in the customer's currency when you can, use 3-D Secure where the issuer supports it, and retry soft declines on a schedule rather than immediately. Some companies also offer stablecoin settlement for customers in markets where card acceptance is unreliable; funds land instantly in the merchant wallet, which is useful for international invoices that would otherwise sit for days.

What the pricing conversation should look like

Ask for interchange-plus or pass-through pricing so the card cost is visible and the processor's margin is a stated markup. Flat-rate bundles look simple, but at SaaS ticket sizes and with a clean B2B mix you are usually overpaying. Ask specifically about: account updater fees, per-token fees, ACH return fees, chargeback fees, and whether there is an early termination clause. A monthly minimum is normal; a three-year auto-renewing contract with liquidated damages is not something a growing software company should sign.

The best time to sort this out is before your billing logic is entangled with a single vendor's API. Get the risk profile, the contract terms and the token portability settled now, and the rest of the stack stays flexible as you grow.