Opening a SaaS merchant account through 2Accept protects the asset a software company actually sells against, its recurring revenue, by boarding you on a dedicated MID with account updater, network tokenization and decline-aware retries attached to every renewal, underwriting your trial flow and annual plans before launch instead of flagging them afterwards, and placing the account behind the billing platform you already run. Our SaaS merchant accounts include B2B subscription software, self-serve and product-led tools, usage-based and API platforms, seat-based team software, vertical SaaS, and annual-contract vendors under a single underwriting relationship.
The process of opening a SaaS merchant account with 2Accept takes four steps. First, complete the online application with your EIN, Articles of Incorporation, three months of bank and processing statements, your monthly recurring revenue and plan mix, the share of customers on annual prepay, your trial and cancellation flow, your billing platform and gateway, and your current chargeback, refund and failed-renewal rates. Second, a dedicated underwriter reviews your billing model, first-attempt renewal decline rate, annual-plan exposure, domestic-to-international split and dispute history within one business hour. Third, you receive a dedicated MID and connect it through an NMI or Authorize.net gateway that your billing platform supports, or through the REST API with hosted fields, after signing the merchant processing agreement. Fourth, you go live in 48 hours with account updater, network tokenization, 3-D Secure 2 and chargeback alerts already configured.
Rates for a SaaS merchant account on 2Accept start at 2.89% + $0.20, with interchange-plus pricing standard above roughly $250,000 a month. Pricing depends on monthly volume, average ticket, the mix of monthly and annual plans, the share of commercial and international cards, chargeback and refund ratios, and how your trial converts to paid, because a trial that surprises customers produces disputes and costs more to underwrite than one that reminds them first.
A software company evaluates a processor on what happens at renewal, not at checkout: how many stored cards still work a year later, how a failed charge is retried, whether an annual-plan campaign is read as growth or as risk, and who answers when a billing run is held. 2Accept covers each of those below and underwrites the SaaS models, billing structures and integrations listed here.
2Accept underwrites the range of software sold on subscription: B2B tools billed per seat, self-serve products that convert a free trial or freemium tier into a paid plan, usage-based and API platforms that bill in arrears, vertical SaaS sold to a single trade, annual-contract vendors with a few large customers, and consumer subscription apps sold on the web. All of them charge a stored card without the customer present, but the cash-flow shape differs, and the shape is what the underwriter reads.
The questions in a SaaS file are specific. How much revenue is collected before it is earned? How does a trial become a charge, and does the customer see it coming? What share of renewals fail on the first attempt, and what happens next? A founder who can answer those three with numbers is usually approved without a second round of questions.
Apply for a SaaS MID →A subscriber who cancels made a decision. A subscriber whose card was reissued after a breach, expired last month, or hit a temporary limit made none, and still lands in your churn number. That involuntary churn is the real cost of card billing for a software company, because each lost renewal takes the remaining lifetime of the account with it. It is also the one part of churn that payment infrastructure, not product, can fix.
2Accept attaches three layers to the MID. Account updater refreshes reissued and expired card numbers from participating issuers before the renewal runs. Network tokens replace the stored card number with a credential the network keeps current. For what still declines, retries are scheduled by decline type: insufficient funds is worth another attempt days later, a closed account is not, and the networks limit and penalise excessive retries.
Apply for Renewal Recovery →A free trial that takes a card up front and converts on its own is the most scrutinised flow in subscription billing. The card networks' rules for it come down to substance: the customer sees and accepts the price, billing date and renewal terms before entering a card, receives a confirmation that repeats them, gets a reminder before the trial becomes a paid plan, and can cancel online without calling anyone. Exact requirements differ by network and change over time, so confirm the current text with your acquirer.
Acquirers study the same flow for a second reason. An unprotected trial sign-up form is where card-testing bots validate stolen numbers, and the resulting authorisations and declines land on your MID. Our underwriters review the sign-up, reminder and cancellation screens before go-live, and the account ships with AVS, CVV and velocity rules sized for a trial form.
Apply for a Trial-Billing MID →An annual plan is the best cash a SaaS company collects and the largest liability its acquirer holds. Twelve months are paid on day one and delivered across the year; if the product shuts down in month four, cardholders dispute and the bank refunds eight months of service it never held the money for. That is future-delivery exposure, and it is why an aggregator's model reacts when a discount campaign shifts your mix toward annual. We underwrite the annual share at approval, so the campaign is expected.
Usage-based and seat-based billing raise a different issue: the amount changes. A stored card should be charged a variable amount only where the customer agreed to that at sign-up, and the strongest dispute file shows the agreement, the usage record and an itemised invoice. Mid-cycle seat additions, proration and overage true-ups run as merchant-initiated transactions flagged against that original consent.
Apply for an Annual-Plan MID →Software sells across borders from the first week, and a cross-border card payment costs more and approves less often than a domestic one: the networks add cross-border assessments, and a foreign issuer is more cautious with a charge presented by a US acquirer. In the EEA and UK, strong customer authentication rules generally require 3-D Secure on the first payment of a new subscription, while later merchant-initiated renewals are generally out of scope when they are flagged correctly.
2Accept places international volume through offshore acquiring where it helps and applies 3-D Secure 2 on the sign-up payment in regulated regions. One limit to know: in-region acquirers usually want a legal entity in their region, so a US-only company gets better routing, not true local acquiring. Sales tax and VAT on software vary by jurisdiction and belong with your tax adviser, not your processor.
Apply for a Cross-Border MID →The MID does not replace your billing system; it sits behind it. Chargebee, Recurly, Maxio and Zuora each connect to third-party gateways, and a 2Accept account connects through an NMI or Authorize.net gateway where the platform supports one. Check your platform's current gateway list before you plan a move. Teams that run their own billing code use the REST API with hosted fields, which keeps card numbers off your servers and your PCI scope small.
Moving a live subscriber base is the part to plan. Stored cards can generally be transferred between PCI-compliant vaults, provider to provider, which needs your current processor's cooperation and takes weeks, not days. Most SaaS companies run both accounts in parallel: new sign-ups on the new MID first, existing subscribers moved in cohorts once the customer mapping is verified.
Apply for a Billing-Platform MID →Merchant accounts are priced by risk tier, and the vertical sets the tier. Subscription software with a clear cancellation path and a clean dispute history underwrites at the low tier, with interchange-plus standard above roughly $250,000 a month. A heavy annual-prepay share, consumer free trials, or a dispute ratio near network limits can move the terms within that tier, usually through a reserve and not through the rate. Rates are average and may vary depending on individual circumstances and risk profile. Interchange may be passed to merchants for more challenging approvals.
Complete the 4-minute application. No credit pull, no application fee, no long-term contract.
A 2Accept underwriter reviews your plan mix, trial flow, annual-prepay share, renewal decline rate, and dispute history within 1 business hour.
Sign your MPA, receive a dedicated MID, and connect it through NMI or Authorize.net behind your billing platform, or through the REST API.
Bill with account updater, network tokens, decline-aware retries, and chargeback alerts working on every renewal cycle from the first one.
Connect your merchant account to the storefront, POS, accounting, and CRM software you already run.
2Accept enables smooth payment operations across Shopify stores.
2Accept connects with Clover POS for seamless point-of-sale transactions.
2Accept syncs payments with QuickBooks to simplify accounting and reconciliation.
2Accept supports BigCommerce to facilitate online payment processing.
2Accept integrates with Authorize.net for secure transactions.
2Accept connects with Salesforce to streamline customer relationship management.
2Accept extends payment capabilities to WooCommerce-powered online stores.
Aggregators made it possible to charge a card on the day a product launches, and for a new SaaS company that is worth a great deal. The cost arrives later. Your subscribers sit in a pooled account whose risk model you cannot see, an annual-plan promotion or a spike in refunds can trigger a hold with no one to call, and pricing stays blended however your card mix changes. A dedicated MID from 2Accept is underwritten for your billing model by a person who has read it.
| Feature | 2Accept | Stripe | Square | PayPal |
|---|---|---|---|---|
| Annual-plan share underwritten before you launch it | ✓ | ✕ | ✕ | ✕ |
| Trial and cancellation flow reviewed before go-live | ✓ | ✕ | ✕ | ✕ |
| Interchange-plus pricing at volume, markup in writing | ✓ | ✕ | ✕ | ✕ |
| Multi-MID routing and failover across acquirers | ✓ | ✕ | ✕ | ✕ |
| Reserve terms agreed in writing at approval | ✓ | ✕ | ✕ | ✕ |
| Dedicated MID (not aggregator pool) | ✓ | ✕ | ✕ | ✕ |
| Human underwriter (not chatbot) | ✓ | ✕ | ✕ | ✕ |
Every 2Accept SaaS merchant account includes the monitoring and mitigation stack that keeps a subscription book well under the card networks' dispute thresholds, where most disputes are unrecognised renewals and forgotten trials, not stolen cards.
Ethoca and Verifi alerts reach you while a dispute is still an inquiry, so a forgotten renewal can be refunded and the subscription cancelled before a chargeback posts.
AVS, CVV and velocity rules on the trial and checkout forms stop card-testing runs, which otherwise fill a SaaS account with small authorisations and later fraud disputes.
3-D Secure 2 on the first payment shifts fraud liability to the issuer on authenticated sign-ups and meets authentication rules for customers in the EEA and UK.
Our dispute team answers with what software can prove: the accepted terms, login and usage after the charge date, and reminder emails, with cases typically resolving within 45 days.
Larger SaaS books are split across 2–5 MIDs so a renewal run is not dependent on one acquirer, and a soft-declined charge can be retried on a second path.
Dynamic descriptors show the product name the user logs in to, not the parent company, which is what stops a team member's manager disputing an unfamiliar charge.
"We thought churn was a product problem. A third of it was cards that had quietly expired. Once account updater and proper retries were running, the number moved without us shipping a single feature."
"We ran an annual-plan promotion and our old processor held payouts for three weeks to review it. This time the underwriter asked about annual share before we launched, which was the right order."
"The trial flow review felt like extra work until our disputes dropped. Adding the reminder email before conversion cost us a few sign-ups and saved us far more in chargebacks."
A SaaS merchant account is a dedicated payment-processing relationship that an acquiring bank issues to a software company billing customers on subscription, structured around stored cards and merchant-initiated renewals, and underwritten for the things that are specific to recurring software revenue: failed renewals, free-trial conversion, annual plans paid in advance, variable usage charges, and customers spread across many countries.
The account permits card-not-present sales through a web checkout, in-app upgrade flow or sales-assisted invoice, stores card credentials for recurring and usage-based charges, and operates under underwriting terms that include account updater and network tokenization on the stored cards, retry logic for declined renewals, 3-D Secure 2 on sign-up payments where it is required or useful, Ethoca and Verifi alerts, Visa Rapid Dispute Resolution, domestic and offshore acquiring, and discount rates from 2.89% + $0.20 or interchange plus a fixed disclosed markup at volume.
Software is not a high-risk product. Nothing ships, nothing is regulated in the way a pharmacy or a gaming site is, and a working product generates few fraud disputes. The risk an acquirer sees is in the billing model. A subscription charges a card the customer is not looking at, so the commonest dispute is a renewal nobody remembers authorising. A free trial that converts silently produces the same dispute in bulk. An annual plan collects twelve months of revenue for service that has not been delivered, which the bank stands behind if the company fails. Aggregators handle all of this with one automated model across a pool of unrelated merchants, which is why a SaaS company's first hold usually follows something that looked like good news: an annual-plan campaign, a price rise, or a month of fast sign-ups. An acquirer underwriting a dedicated account weighs the cancellation path, the trial disclosures, the annual share, refund policy and runway.
Opening a SaaS merchant account differs from signing up with an aggregator in three ways. First, the billing model is read before the account is live: trial screens, reminder emails, cancellation path and annual-plan share are reviewed by an underwriter, so the terms you are approved on already account for them. Second, the stored card is treated as the asset it is, with account updater, network tokens and decline-type retries protecting each renewal instead of a single failed charge ending the subscription. Third, the account belongs to your company alone, sits behind the billing platform you choose, and can be split across more than one acquirer as the book grows.
2Accept underwrites SaaS merchant accounts for B2B subscription software, self-serve and product-led tools, usage-based and API platforms, vertical SaaS, annual-contract vendors and consumer subscription apps across the United States. Applications are reviewed by a dedicated underwriter within one business hour and are typically live in 48 hours depending on documentation, then connected through NMI or Authorize.net behind a billing platform, or through the REST API, after signing the merchant processing agreement.
Acquiring banks segment software companies by how and when the money is collected, not by what the software does. The SaaS businesses 2Accept underwrites most often are:
A dedicated SaaS merchant account gives a software company things a pooled aggregator account cannot, because the terms are set for your billing model by someone who has reviewed it and the renewal tooling is part of the account, not an add-on:
Qualifying for a SaaS merchant account means showing the acquiring bank how you bill, how customers cancel, and how much revenue you hold before earning it. Standard qualification criteria include:
Keeping a SaaS merchant account healthy is mostly a matter of making sure no customer is surprised by a charge, and of treating a failed renewal as recoverable. Acquirers review accounts on a rolling basis and the card networks run monitoring programmes for merchants whose dispute or fraud levels run high, so the habits below protect both revenue and the MID:
No. Accounts run month-to-month, with no long-term commitment and no early-termination fee if you leave.
Your EIN and formation documents, three months of bank and processing statements, an MRR and plan-mix breakdown, screenshots or a test login for sign-up and cancellation, your billing platform and gateway, and ID for each principal owner.
Yes. Without processing history the file rests on the product being live, the pricing and cancellation pages, the founders' background and bank statements. Expect conservative starting volume limits that are raised as history builds.
Yes, and it is a common reason SaaS companies apply. Tell us what triggered the hold. If it was an annual-plan campaign or a refund spike, that is context an underwriter can work with.
For a domestic MID, yes: a U.S. entity, EIN and U.S. bank account. Founders based abroad with a U.S. company are boarded regularly.
No. It is one input. The billing model, dispute history, bank statements and runway carry more weight in a software file.
Through NMI or Authorize.net behind a billing platform that supports them, through the REST API with hosted fields if you run your own billing, or with a hosted payment page for the simplest set-up.
No. Applying and the underwriting review cost nothing.
The low tier starts at 2.89% + $0.20. Above roughly $250,000 a month, interchange-plus is standard: actual interchange passed through plus a fixed markup you see in writing before signing.
Sometimes, and not always. At low volume the headline rates are close and an aggregator bundles billing tools you would otherwise pay for. The saving appears at volume on interchange-plus, and in recovered renewals, which are usually worth more than the rate difference. Send a statement and we will give you the comparison either way.
Yes. The card networks add cross-border assessments when the card is issued outside the acquirer's country, and those are passed through. The cost is set by the networks, not by us, and applies at every processor.
Possibly. Where a reserve applies it is 0–10% and is set at approval. A large annual share with limited runway is the usual reason; a history of clean renewals is the usual reason it is waived or reduced.
They can. Corporate and purchasing cards qualify for lower commercial interchange when extra invoice fields are sent. The benefit is real mainly on larger invoices paid with commercial cards on interchange-plus.
Any per-update or per-token fees are itemised in your pricing schedule before you sign. Compare them with the revenue of a single recovered subscriber over its remaining lifetime; the arithmetic is rarely close.
Next-day funding is typical. Reserve and funding terms, where they apply, are written into the approval.
Commonly $15–$25 per dispute, set out in your agreement. Alerts that let you refund before a chargeback posts keep the count low.
Subscribers lost because a payment failed, not because they chose to leave: expired or reissued cards, temporary limits, issuer caution. It is separate from voluntary churn and largely recoverable with the right payment set-up.
Before a renewal, stored cards are checked against updates that participating issuers send to Visa and Mastercard. New numbers and expiry dates come back and the charge runs on the current card.
The card number in your vault is replaced by a token issued by the card network, which the network keeps linked to the current card when it is reissued.
A soft decline is temporary, such as insufficient funds or an issuer time-out. A hard decline is final, such as a closed account or a stolen card.
A few, spaced over days, and only on soft declines. The card networks limit retries on a declined card and charge fees for excess, so retry schedules need a hard stop.
No, and it is better to say so plainly. Dunning emails, in-app banners and grace periods belong to your billing platform, which knows the customer and the plan. We supply the card-level layer underneath it: updater, tokens, correct flagging and decline codes detailed enough to drive your retry rules. If you have no billing platform yet, choose one before migrating.
It can dip briefly if stored credentials are not migrated with their original transaction references. We plan the migration so renewals stay flagged as an existing agreement.
Split last quarter's lost subscribers into cancelled and failed-payment. If your billing platform cannot report that, your statements and decline codes can. We will go through it with you as part of the review.
In substance: clear disclosure of the price and billing date before the card is entered, the customer's consent to them, a confirmation, a reminder before the first paid charge, and a simple online way to cancel. Details differ by network, so check current rules with your acquirer.
Yes. If the customer enters a card only when choosing to pay, there is no silent conversion to dispute. Card-up-front trials are approved too, with the disclosures in place.
Because the bank is liable for service not yet delivered. If a company stops operating mid-year, cardholders can dispute the unused months, and the acquirer pays if the merchant cannot.
Multi-year plans are reviewed case by case and often carry a reserve. Lifetime deals are harder: the delivery period has no end, and some banks decline them.
State in your terms that the amount varies with usage, capture consent at sign-up, send an itemised invoice before or with each charge, and keep the usage records.
Yes, where your terms cover it. Prorated seat charges run as merchant-initiated transactions against the stored credential.
No. Tax on software differs by state and country; use a tax engine and adviser.
It causes disputes when customers learn of it from their statement. Give notice ahead of the first charge at the new price and warn your underwriter.
Mostly unrecognised or forgotten renewals, charges after a customer believes they cancelled, trials that converted unnoticed, and a smaller share of true fraud from stolen cards used at sign-up.
Fraudsters run stolen card numbers through a low-value or zero-value form to see which are live. Trial forms are ideal for it unless velocity limits and CVV checks are in place.
The terms the customer accepted with a timestamp, the receipt and reminder emails, and login or usage records after the charge date. For fraud claims, prior undisputed payments from the same account and device help.
It shifts liability for fraud disputes on authenticated payments. It does nothing for a customer who says they cancelled.
Our dispute team files the evidence, and cases typically resolve within 45 days.
Acquirers want to see well under 1% of transactions, and the networks monitor both ratios and counts. We track both monthly.
Ethoca and Verifi pass on the issuer's notice when a cardholder questions a charge. You refund and cancel the plan, and the case usually closes without becoming a chargeback.
A Verifi service that refunds eligible Visa disputes automatically, under rules you set by amount and reason, at the pre-dispute stage before they turn into chargebacks.
Stripe gives you instant onboarding and built-in billing on a pooled account with automated risk decisions. 2Accept gives you a dedicated MID underwritten for your billing model, behind the billing platform you pick.
If you are early, mostly on monthly plans, have never had a hold and rely on the aggregator's own billing product, staying put is reasonable. The case for moving builds with annual-plan share, volume, and the first unexplained payout delay.
It is a project, and we will not pretend otherwise. Subscription logic, webhooks, invoices and the card vault all have to move or be bridged. Stored cards can generally be exported to another PCI-compliant provider on request. Many teams adopt a gateway-neutral billing platform first and switch acquirers second.
Yes. Many SaaS companies route new sign-ups to the new MID and keep existing subscribers where they are until migrated.
App-store billing follows the stores' own rules and commissions, and is outside a merchant account. Where the stores allow web purchase, a MID handles the web checkout; check the current store policies for your app category.
No. They are gateways that carry the transaction. The MID behind them is the merchant account we provide.
A merchant of record resells your product and handles tax for a higher fee. It suits small teams selling worldwide.
Domestic for a U.S. company with mostly U.S. customers. Offshore placement is added when international volume or the business model calls for it.
Send us a recent statement and your plan mix and we'll show you how much of your churn is failed payments and what your annual plans mean for terms. The review is free, there's no application fee, and an underwriter replies within one business hour.
Start Your ApplicationSoftware companies rarely stay a pure subscription business. A CRM vendor starts letting its customers take payments inside the product, a studio that builds sites turns its care plans into a hosted platform, a marketing agency productises its reporting into a paid tool, and a successful app adds an e-commerce store or an enterprise tier with invoiced contracts. Each underwrites on a different basis even when the brand is the same. 2Accept underwrites these adjacent categories under the same acquiring relationships, so one operator can hold several MIDs without starting underwriting again.
If your software business runs more than one product or entity, for example a core subscription product, a separate usage-billed API, and a services arm that invoices onboarding and custom work, 2Accept can structure a separate MID for each under one underwriting relationship. Each MID carries its own descriptor and its own dispute ratio, so a refund spike after a pricing change on one product does not affect renewals on the others.
Apply now and let's build your business — without hesitation.
SPEAK TO A PAYMENT EXPERT