SaaS Merchant Account: What It Is and How to Get One

A SaaS merchant account is a bank-sponsored account that lets a software company accept card payments for subscriptions, seats, usage fees, and annual plans, then settle those funds to its business bank account. Most SaaS companies qualify through a standard underwriting review, but recurring billing, free trials, and refund policies all shape the outcome. This guide explains how a SaaS merchant account works, what underwriters look for, and the exact steps and documents you need to apply.

What is a SaaS merchant account?

A merchant account is the account an acquiring bank opens for your business so you can accept card payments. When a customer pays, the funds land in the merchant account first, then settle to your business checking account, usually within a few business days.

A SaaS merchant account is the same core product, set up and underwritten for software billing. That means it is built to handle card-not-present transactions, stored card credentials, and recurring charges on monthly or annual cycles. If you want the full picture of how SaaS billing fits together, see our SaaS and marketplace payment processing page.

A SaaS payment stack usually has three parts:

• Merchant account: where approved card funds are held before settlement.
• Payment gateway: the software that securely sends card data from your app or checkout to the processor, and often stores cards for future billing. Payment Circle works with NMI and Authorize.net; learn more on our payment gateways page.
• Billing logic: your subscription platform or in-house code that decides when to charge, how much, and what happens when a charge fails.

Do SaaS companies need their own merchant account?

Not always on day one. Many early-stage software companies start on an all-in-one payment platform, which places many businesses under one shared master account. That is fast to set up, but your account can be reviewed, paused, or closed with little notice if your transaction pattern changes.

A dedicated SaaS merchant account starts to make sense when one or more of these is true:

• Your monthly processing volume is growing and you want pricing tied to your actual card mix.
• You sell larger annual plans or enterprise contracts, where a single held payment would hurt cash flow.
• You want direct control over gateway choice, stored-card tokens, and retry logic.
• You manage billing for clients (for example, an agency or software house running payments for its customers) and need a stable, predictable setup.

The right moment to switch depends on volume, ticket size, and how much a sudden account freeze would cost your business.

Shared payment platform vs dedicated SaaS merchant account

Is SaaS considered high-risk?

Most B2B software with clear pricing and a low refund rate is reviewed as a standard, lower-risk business. Risk rises with certain features, not with the word “SaaS” itself. Underwriters pay closer attention when a software business has:

• Free trials that convert to paid plans, which can cause “I didn’t know I’d be charged” disputes.
• Consumer (B2C) subscriptions sold through paid ads, where buyers are less invested.
• Long prepaid terms (annual or multi-year), since the bank carries the risk of refunds if the service stops.
• High-ticket plans or sudden spikes in volume.
• Weak cancellation flows that push customers to dispute charges with their bank instead.

If several of these apply, your account may be placed in a higher pricing tier or come with a reserve. Read what makes a business high-risk for the full list of factors, or visit our high-risk merchant accounts page if your model fits that profile.

What underwriters review for a SaaS merchant account

Underwriting is the bank’s review of how likely your business is to cause losses through chargebacks, refunds, or fraud. For software companies, the review usually centers on five areas. Here is what to prepare for each one.

1. Billing model and pricing page

Underwriters want to see exactly what customers pay and when. A public pricing page with plan names, billing frequency (monthly, annual, usage-based), and what each tier includes builds confidence quickly.

2. Free trial and consent flow

If you offer a free trial that rolls into a paid plan, card network rules apply. Visa’s subscription rules for trials and introductory offers require merchants to get the cardholder’s express consent to the ongoing subscription, email a copy of the terms with a simple online cancellation link, and send a reminder at least seven days before the first recurring charge after a trial or promo period ends. Underwriters often ask to see screenshots of this flow.

3. Cancellation and refund policy

The Federal Trade Commission’s enforcement policy statement on negative option marketing expects sellers of automatic renewals to clearly disclose material terms, get express informed consent before charging, and offer a simple way to cancel. For online sales, the Restore Online Shoppers’ Confidence Act (ROSCA) applies these same principles. Many states also have their own auto-renewal laws, so check the rules where your customers live.

4. Processing history and chargebacks

If you have processed before, expect to share recent processing statements. Underwriters look at your monthly volume, average ticket, refund rate, and chargeback ratio. A low, stable chargeback ratio is one of the strongest signals you can show.

5. Data security

Any business that stores, processes, or transmits cardholder data falls within scope of the PCI Data Security Standard (PCI DSS). Most SaaS companies shrink their PCI scope by using the gateway’s hosted payment fields and card vault, so raw card numbers never touch their own servers. Be ready to explain how card data flows through your app.

How to get a SaaS merchant account: step by step

1. Map your billing model. List every plan, price, billing cycle, trial length, and add-on. Estimate monthly volume, average transaction size, and your largest single charge.
2. Clean up your website. Make sure your pricing page, terms of service, privacy policy, refund policy, and contact details (business address, phone, support email) are live and easy to find.
3. Fix your trial and cancellation flow. Add a clear consent checkbox or statement at signup, a trial-ending reminder, and a self-serve cancel button in the account settings.
4. Gather your documents. Use the checklist below so nothing slows down the review.
5. Choose your gateway. Decide whether NMI or Authorize.net fits your stack, and confirm it supports stored cards and recurring billing for your subscription platform.
6. Submit your application. Answer billing and refund questions honestly; mismatches between your application and website are a common cause of delays.
7. Review your terms. Read the pricing tier, any reserve, and the contract length before you sign. Our pricing page explains how our interchange-plus tiers work.
8. Test, then go live. Run test charges, test a failed payment and retry, and confirm settlement reaches your bank account before switching real customers over.

SaaS merchant account application checklist

Requirements vary by bank, but most applications ask for the items below. For a fuller list, use our merchant account approval checklist.

• ☐ Business formation documents and EIN
• ☐ Government-issued photo ID for each principal owner
• ☐ Business bank account details (often a voided check or bank letter)
• ☐ Recent processing statements (if you have processed before)
• ☐ Recent business bank statements
• ☐ Website URL with live pricing, terms, privacy, and refund policies
• ☐ Screenshots of your signup, trial consent, and cancellation flow
• ☐ Estimated monthly volume, average ticket, and highest ticket
• ☐ Description of who your customers are (B2B, B2C, or both) and how you acquire them
• ☐ Name of your gateway and subscription billing platform

Worked example: a B2B SaaS with monthly and annual plans

Picture a project-management tool with two plans: $49 per month or $490 per year. It offers a 14-day free trial that requires a card at signup, and 70% of customers are small agencies.

Here is what an underwriter would likely focus on:

• The trial. Does signup clearly state the post-trial price and date? Is a reminder sent at least seven days before the first charge, as Visa requires for trials?
• The annual plan. The $490 charge is the largest ticket, so the bank wants to know your refund terms if a customer cancels mid-year.
• Chargebacks. Low historical disputes and fast support response times are strong signals.

With those answered clearly, this business would usually fit a standard online tier. If the same product sold to consumers through aggressive ad funnels with hidden trial terms, the risk picture (and pricing) would look very different.

Features to look for in a SaaS payment setup

• Card vault and tokenization: stores card credentials securely so you can bill renewals without holding card numbers yourself.
• Recurring billing support: works with your subscription platform for monthly, annual, and usage-based charges. Our guide on how to accept recurring payments walks through the setup.
• Account updater: card networks offer services such as Visa Account Updater, which helps merchants get updated card details and reduce declines when cards are reissued or expire.
• Smart retries and dunning: automatic retries and customer emails when a renewal fails.
• Chargeback tools: alerts and evidence workflows. See our chargeback management services.
• ACH option: a bank-payment alternative for larger invoices.

Should SaaS companies accept ACH too?

For B2B software, often yes. ACH moves money directly between bank accounts, and according to Nacha, about 80% of ACH payments settle in one banking day or less. Bank accounts also do not expire the way cards do, which can reduce involuntary churn on annual renewals.

The trade-off is that ACH debits need proper customer authorization and can be returned. Many SaaS companies offer cards for monthly plans and ACH for annual or enterprise invoices. Explore our ACH payment processing options and confirm your authorization wording before you launch.

Common mistakes that slow SaaS approvals

• Hidden pricing. “Contact us for pricing” on every plan makes it hard for underwriters to judge ticket size.
• No visible refund policy. Even a “no refunds after renewal” policy is better than none, as long as it is clearly disclosed.
• Burying the cancel option. Requiring a phone call or email to cancel invites disputes.
• Underestimating volume. Processing far above your stated volume can trigger a review or hold. Update your provider before a big launch.
• Mismatched business details. The legal name, address, and descriptor on your application should match your website and bank records.

Related guides and next steps

• Comparing SaaS payment options? See our SaaS payment processing solutions.
• Running subscriptions or memberships? Visit subscription payment processing.
• New to merchant accounts? Start with our merchant accounts overview.
• Not sure which risk tier you fall into? Read high-risk vs low-risk merchant accounts.
• Want to understand your rates? See how our interchange-plus pricing tiers work.
• Building a platform that pays out to users? Compare payment facilitator vs merchant account models.
• Ready to apply? Start your merchant account application.

Frequently asked questions

How long does it take to get a SaaS merchant account?

Timing depends on the bank, your risk profile, and how complete your application is. A business with a clean website and all documents ready usually moves faster. Missing policies or unclear billing details are the most common reasons for back-and-forth.

Can a new SaaS startup with no processing history get a merchant account?

Yes, many banks review new businesses. Without statements, underwriters lean more on your website, pricing, policies, owner background, and business bank statements. Realistic volume estimates help.

Do I need a different merchant account for annual plans?

No. One merchant account can handle monthly and annual billing. Just disclose your annual plans and largest ticket size on the application, since prepaid terms affect how the bank views risk.

Will offering a free trial affect my approval?

It can affect your risk review, but a well-built trial is common and acceptable. Clear consent at signup, a reminder before the first charge, and easy online cancellation line up with Visa’s trial rules and lower your dispute risk.

What payment gateway works best for SaaS?

Look for a gateway with a secure card vault, recurring billing support, and integrations with your subscription platform. Payment Circle supports NMI and Authorize.net, and we can help you match one to your tech stack.

Sources and further reading

• Visa: Trial Subscription Updates (subscription merchant requirements)
• Federal Trade Commission: Enforcement Policy Statement Regarding Negative Option Marketing
• PCI Security Standards Council: PCI Data Security Standard (PCI DSS)
• Visa Developer: Visa Account Updater
• Nacha: How ACH Payments Work

Get a SaaS merchant account built for recurring billing

Payment Circle helps new U.S. software companies, agencies, and software houses set up merchant accounts with clear interchange-plus pricing, simple contract terms, and NMI or Authorize.net gateways. Start your application or call us at (571) 274-7950, 9:00 AM–6:00 PM Eastern. Prefer email? Contact our team.