Payment processing for software and SaaS merchants in September 2026
Why many SaaS apps board easily until a feature trips AUP — scraping, adult, crypto, or gambling tools — and how to settle subscriptions without a platform freeze.
Independent vertical brief · Updated September 2026 · Reviewed by Phil Lawrence
We review high-risk payment rails across commercial verticals. We recommend one provider and earn an affiliate commission if you create an account through our links. It costs you nothing extra, and we state plainly who should not use it.
AT A GLANCE — Software & SaaS Underwriting Profile
Industry ranges are compiled from public sources and vary by acquirer, jurisdiction and merchant profile. RiskPay figures are from the provider's published pricing.
01 — Structural Risk
Why this vertical gets declined
SaaS is not high-risk until the feature set is. Aggregators underwrite the use case, not the React app. A product that helps merchants scrape, spam, or operate in banned verticals inherits that vertical’s ban.
Four tripwires:
01. End-use AUP
If your app’s happy path is a prohibited business, your MID is that business. “We just sell software” does not survive review.
02. Trial conversion patterns
Cheap trials that convert to full price without a clear reminder are negative-option digital goods.
03. Seat vs usage surprises
Metered bills that spike month-over-month look like fraud or unrecognized charges.
04. Chargeback-prone SMBs
Prosumer tools sold on ads behave like info products, not like enterprise SaaS with ACH.
02 — The Fallout
What actually happens when you get shut down
SaaS freezes strand prepaid annual plans. Customers still expect uptime while you cannot pay cloud invoices from the platform balance.
- 01
Feature or landing-page recode
A new scraper, adult filter, or cannabis module recodes the whole file.
- 02
Payouts stopped
MRR sits in custodial limbo. Infrastructure invoices do not wait.
- 03
AUP termination
Notice cites the restricted use case, not your uptime.
- 04
Hold of prepaid annuals
Unused subscription months are treated as unshipped digital goods. Terms vary.
- 05
MATCH exposure
Especially if the recode was fraud or illegal-activity coded.
What Traditional Recovery Looks Like
Merchants seeking emergency replacement accounts for software and SaaS merchants through high-risk Independent Sales Organizations typically encounter non-refundable application fees, rolling reserves held for months, elevated discount rates, and delayed international wires. Those terms vary by acquirer and jurisdiction — confirm directly.
Table 1 — SaaS operational baseline
Requirements checklist
Document the use case honestly. A second “clean” website that hides the scraper will be found.
| Requirement | Standard / Specification | Why Acquirers Demand It | Protocol on Non-Custodial Rails |
|---|---|---|---|
| Honest positioning | Marketing matches the actual product | AUP recode | Merchant-governed |
| Trial disclosure | Price, date, cancel path before the trial ends | Negative-option digital goods | Merchant discretion |
| Descriptor | Product name users typed | Unrecognized SaaS rebills | Configurable in dashboard |
| Cancel in-app | Self-serve cancel, not “email success@” | Subscription regulation and disputes | Product |
| Metered invoices | Usage caps or alerts before a surprise bill | Unrecognized usage charges | Billing design |
Table 2 — Effective processing cost per $10,000 processed
What it costs
Stated assumption: Based on $10,000 monthly volume. Figures include the plan subscription fee (annual plans allocated monthly as one-twelfth of the annual cost) and exclude the provider fee (typically 1.5%–4.5%), which is billed separately.
| Plan / Billing | Gateway % | Gateway $ | Allocated Subscription | Total on $10k |
|---|---|---|---|---|
| Free ($0/mo) | 12% | $1,200 | $0 | $1,200 |
| Scale monthly ($99/mo) | 10% | $1,000 | $99 | $1,099 |
| Scale yearly ($1,188/yr) | 7% | $700 | $99 | $799 |
| MAX monthly ($199/mo) | 8% | $800 | $199 | $999 |
| MAX yearly ($1,899/yr) | 6% | $600 | $158 | $758 |
Footnote: Scale yearly calculates as $10,000 × 7% + ($1,188 ÷ 12) = $799. MAX yearly calculates as $10,000 × 6% + ($1,899 ÷ 12) = $758.25 (rounded to $758). For a detailed cost model including volume break-evens, visit our pricing breakdown.
03 — Practical Architecture
Recommended setup
If you already know Stripe will recode you after the next feature ships, do not build MRR on their balance.
Self-hosted WordPress + WooCommerce
Your app’s billing portal or WooCommerce for simple tools. Own the customer list.
RiskPay WooCommerce plugin
Install the official RiskPay extension. Customers pay with cards, Apple Pay, or Google Pay. No forced crypto checkout. The provider does not use API keys.
Self-custody Polygon wallet
YOUR WALLET ADDRESS on Polygon. Annual prepay should not sit at an aggregator. The recommended provider does not use API keys.
Institutional exchange off-ramp
Hold operating reserves in USDC where useful. Off-ramp to corporate fiat for payroll, ads platforms that require it, and taxes.
Ready to stabilize your checkout?
Bill SaaS cards without parking prepaid MRR in a freezeable platform balance.
04 — Margin Threshold
Where this is not the right fit
Software usually clears a 25% gross margin threshold easily, which is why the fee can be rational.
If you sell someone else’s white-label at thin reseller margin below that threshold, do not use this rail.
Infrastructure-heavy products must count COGS. If margin after COGS is thin, 6%–12% on gross billing will crush you.
05 — Storefront Optimization
Integration notes for SaaS merchants
Provisioning must follow webhooks. Do not leave seats active after a failed rebill if you intend to collect.
Subscription webhooks
Paid → provision. Failed → dunning then suspend. Refunded → revoke.
Seat changes
Proration should appear as a recognizable descriptor, not a random extra charge.
Annual invoices
High annual tickets deserve a hosted invoice and a PDF receipt.
06 — Questions
Frequently asked questions
My SaaS is B2B. Why would I ever need high-risk rails?
Because aggregators underwrite features. A B2B scraper, adult CMS, cannabis POS, or gambling widget inherits those AUPs.
5817 vs 5734 — which MCC?
5734 is the classic computer software stores MCC. 5817 is digital-goods software. Online-delivered SaaS is commonly in that digital-goods family.
Can I keep Stripe for clean plans and RiskPay for restricted ones?
Splitting catalogs is how platforms accuse you of hiding. If the product is restricted, assume the restricted rail.
Do you use API keys?
The recommended provider does not use API keys. WooCommerce plugin plus a Polygon wallet address is the published setup.
How do refunds work for unused seats?
You refund from treasury. Policy should be written. Instant settlement is not a no-refund license.
07 — Related Guides & Resources
Related payment guides
Pricing Guide
6%–12% Fee Breakdown & Breakeven Math
A complete breakdown of plan tiers, provider fees, and volume thresholds across high-risk e-commerce.
MCC codes
Why MCC codes affect approval
How merchant category codes are assigned and why a mismatch can block or terminate processing.
Chargebacks
How to calculate your chargeback ratio
Dispute lifecycle, monitoring programs, and the operational levers that reduce dispute volume.
Declined
What to do after a processor shutdown
Triage for declined, frozen, and terminated accounts, including held funds and next rails.
Sibling Vertical
Recurring billing and subscriptions
The billing pattern itself, across products.
Sibling Vertical
Digital products and ebooks
One-time files versus ongoing seats.
Last reviewed September 2026
Related verticals in this group