---
title: "Payment processing for SaaS: how to set up billing, checkout, and tax (step by step)"
slug: payment-processing-for-saas
excerpt: "A step-by-step guide to setting up payment processing for a SaaS product: billing model, processor, merchant of record or all-in-one platform, checkout, billing layer, tax, and testing, with real cost at $10k and $100k MRR."
customExcerpt: "A step-by-step guide to setting up payment processing for a SaaS product: billing model, processor, merchant of record or all-in-one platform, checkout, billing layer, tax, and testing, with real cost at $10k and $100k MRR."
metaTitle: "Payment processing for SaaS: Billing, checkout, and tax"
metaDescription: "A guide to setting up payments for a SaaS product, including how to choose between a processor, merchant of record or all-in-one platform."
featureImage: "https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/images/2026/11/saas-payment-processing.png"
status: published
publishedAt: "2026-11-18T20:07:05.000Z"
updatedAt: "2026-11-18T20:07:05.000Z"
createdAt: "2026-11-11T12:04:36.820Z"
tags:
  - { name: Payments, slug: payments }
  - { name: SaaS, slug: saas }
authors:
  - { name: Liv Carr, slug: oliviacarr }
  - { name: Keisha Singleton, slug: keisha }
---

# Payment processing for SaaS: how to set up billing, checkout, and tax (step by step)

SaaS [payment processing](https://whop.com/blog/payment-processors/) varies widely across businesses, but it's the most important thing to get right. 

Most SaaS businesses have specific needs beyond simple payment acceptance, which means founders often look for a unified solution that takes care of automated billing, tax, and managing subscription access. 

The good news is, you can set up the entire payment processing flow for your SaaS business in 7 steps, including choosing your billing model, provider, and configuring checkout. 

We'll walk you through each step below, and compare effective costs at $10k and $100k MRR.

## What a SaaS payment stack actually needs

When you sell subscriptions, you're still managing payments long after the first checkout. Customers renew, switch plans, and cancel, so your payment stack needs to cover:

- **Payment method acceptance:** Methods you can easily charge again at renewal.
- [**Recurring billing**](https://whop.com/blog/saas-billing/)**:** Tracking renewals, cancellations, and mid-cycle plan changes.
- **Hosted or embedded checkout:** Allowing customers to choose a plan and see what they'll pay both now and at renewal.
- **Tax calculation and remittance:** Applying the right tax to recurring charges and remitting it where required.
- **Dunning and failed payment recovery:** Retrying failed renewals and prompting customers to update expired cards before they lose access.
- **Invoicing:** Issuing invoices for renewals and mid-cycle upgrades.
- **Subscription access:** Giving customers access to the features they pay for and updating it when their plan changes or ends.
- **Chargeback handling:** Using billing and cancellation records to respond to disputed renewals.
- **Reporting:** Tracking monthly recurring revenue, upgrades, downgrades, and [churn](https://whop.com/blog/what-is-churn/) alongside sales.

You can use separate tools to assemble your own subscription payment processing stack, but that's time-consuming – and often more expensive than using one provider that handles most moving parts. 

### How SaaS startups should process payments before product-market fit

Before your SaaS has product-market fit (PMF) – including growing demand and retention – you don't need to spend huge amounts to build a custom setup for your payment processing.

The simplest way to get set up is to start with hosted checkout on an all-in-one platform with tax handled. An all-in-one provider means little to no engineering time, configurations for product plans and pricing, and having everything housed in one place. 

And if you have some dev resources, most complete solutions offer API capabilities to customize your [subscription billing](https://whop.com/blog/subscription-billing-software/), too.

You can change setups down the road, but be aware that moving saved customer cards to a new provider isn’t always possible, so check before you commit. Step 7 covers this in more detail.

## Set up payment processing for your SaaS in 7 steps

Below are the 7 steps to get your payments, checkout, billing layer, tax responsibility, and fraud prevention set up and running on autopilot.

### Step 1: Pick your billing model

The first decision you'll need to be clear on is your billing model – i.e., how you charge for your SaaS: flat rate, price per user, or usage-based. 

That choice affects which provider has the necessary stack for your business needs throughout the payment lifecycle.

#### Billing models compared

Flat tier, per-seat, and usage-based models require different things from your payment stack, and not all providers offer the same functionality. 

<table>
  <thead>
    <tr>
      <th>Model</th>
      <th>Best for</th>
      <th>Your payment stack needs</th>
      <th>Example</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Flat</strong></td>
      <td>One price per plan, same value for every customer</td>
      <td>Recurring plans, trials, tier upgrades, and payment retries</td>
      <td>Basecamp: $199/month billed annually, unlimited users</td>
    </tr>
    <tr>
      <td><strong>Per-seat</strong></td>
      <td>Team tools where value grows with each user</td>
      <td>Seat counts, mid-cycle proration, and access per seat</td>
      <td>Linear: $10–$16 per user/month, billed yearly</td>
    </tr>
    <tr>
      <td><strong>Usage or hybrid</strong></td>
      <td>Products where cost scales with use, like API calls or AI actions</td>
      <td>Usage metering, end-of-period invoicing, and saved cards charged automatically</td>
      <td>Intercom: seats plus $0.99 per AI-resolved conversation</td>
    </tr>
  </tbody>
</table>

#### Start with flat tiers

Flat tiers are often the simplest place to start, especially if you're an early-stage SaaS startup. 

Give each plan a fixed price and spell out what's included. That makes it easier to bill customers, test what they'll pay for, and explain the difference between plans. 

If your provider supports per-seat and usage-based billing, you can add either later without switching. On Whop, you can track usage in your own app and charge customers’ saved payment methods through the API.

### Step 2: Choose a processor, a merchant of record, or an all-in-one platform

Once you've chosen your billing model, you can choose whether you'll use a payment processor, merchant of record, or all-in-one platform to manage your payments.

The setup you choose determines how much of steps 3 to 7 you'll build yourself, from configuring checkout to testing the subscription flow before you go live.

> I have built dozens of SaaS apps, and finding a payment provider can be deceptively hard. One thing that I would recommend everyone to check is that your use case is allowed in the provider’s TOS. For example many of the most used payment platforms do not allow SaaS apps that are based on AI image generation. 
> 
> – Colin McDermott, Whop Head of SEO/GEO

#### Option 1: A payment processor

If you use a processor like [Stripe](https://whop.com/blog/what-is-stripe/) or Adyen to accept payments, you're still the seller of record and responsible for tax, refunds, chargebacks, and compliance. 

You can get subscription billing, retries, recurring invoices, and tax tools from Stripe itself (or bring in separate tools), but your team still needs to connect billing to your app so access updates when customers upgrade, cancel, or miss a payment. 

That gives you the most control over how the stack fits together, but it's more work for your team to maintain every moving part.

Read our review of [Whop vs Stripe](https://whop.com/blog/whop-vs-stripe/) for a complete head-to-head comparison of each provider's capabilities.

#### Option 2: A merchant of record

A merchant of record (MoR) like Paddle or [Lemon Squeezy](https://whop.com/blog/lemon-squeezy-alternatives/) acts as the legal seller for transactions it handles, taking care of sales tax, refunds, and chargebacks – in exchange for a higher transaction fee. 

Paddle's pay-as-you-go transaction rate, for example, is 5% + $0.50, vs Stripe's 2.9% + $0.30, and Whop's 2.7% + $0.30. However, Paddle includes billing as part of that rate, whereas it costs an extra 0.7% per transaction with Stripe, and an extra 0.5% per transaction with Whop.

Stripe also offers a merchant-of-record product called Managed Payments, which costs 3.5% per transaction on top of payment processing fees.

With a merchant of record, its name also appears on the customer receipt, and you typically have less control over checkout customization and the customer data you can collect.

#### Option 3: An all-in-one platform

All-in-one providers like Whop let you configure hosted or embedded checkout, take recurring payments, manage subscription access and customer invoicing, send payouts, and host your website in one place. 

You stay the seller of your product and can handle tax yourself, have Whop calculate and collect it at checkout and remit it yourself, or have Whop calculate, collect, and remit it in supported jurisdictions.

Each extra (billing, tax, [payment orchestration](https://whop.com/blog/payment-orchestration/)) is charged per transaction, with no monthly fees. 

#### Effective cost at $10k and $100k MRR

So what does each option cost you? As an example, we'll imagine a business charging $50 flat rate subscriptions, at both $10k MRR (200 payments) and $100k MRR (2,000 payments). Each assumes all payments are via domestic cards, with a 0.5% dispute rate, and tax handling included.

<table style="table-layout: fixed; width: 100%;">
  <colgroup>
    <col style="width: 16%;">
    <col style="width: 28%;">
    <col style="width: 28%;">
    <col style="width: 28%;">
  </colgroup>
  <thead>
    <tr>
      <th style="vertical-align: top;">MRR</th>
      <th style="vertical-align: top;">Processor (Stripe)</th>
      <th style="vertical-align: top;">MoR (Paddle)</th>
      <th style="vertical-align: top;">All-in-one (Whop)</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>$10k</strong></td>
      <td>$525/month</td>
      <td>$600/month</td>
      <td>$595/month</td>
    </tr>
    <tr>
      <td><strong>$100k</strong></td>
      <td>$5,260/month</td>
      <td>$6,000/month</td>
      <td>$5,950/month</td>
    </tr>
  </tbody>
</table>

<p><small>Published rates checked November 2026. The table covers provider fees. If your SaaS runs in a separate app, factor in the work to connect subscription status to customer access with whichever provider you choose. You can build and host your product on Whop, accessing built-in access controls.</small></p>

If 40% of your payments come from cards issued abroad, add about $60 a month at $10k MRR (and $600 at $100k MRR) to both the Stripe and Whop totals for their 1.5% international card fee. Paddle’s 5% + $0.50 stays the same.

- The Stripe totals include card processing at 2.9% + $0.30, Billing at 0.7%, Tax Complete at $90 a month at $10k MRR, or $430 plus $0.48 per transaction over 1,000 at $100k MRR (about $910), and $15 per dispute. Billing covers payment retries and subscription invoices. At $10k MRR, that's a total of $525. At $100k MRR, it's $5,260. You stay the seller of record, so you control how checkout and billing are set up and remain responsible for refunds, disputes, and tax compliance.
- Paddle's 5% + $0.50 per payment comes to $600 and $6,000, assuming no paid add-ons. That fee includes subscription billing, tax handling, and chargeback management. Paddle is the legal seller on those transactions and appears on the receipt. You hand over more of the work and have less control over checkout and what customer data you collect there.
- Whop's standard rate is 2.7% + $0.30 per payment, 0.5% for Billing, and $15 per dispute. That comes to $395 and $3,950 before optional tax. You stay the seller, and the [Whop Tax Service](https://whop.com/blog/whop-tax-service/) 2% transaction fee applies only to payments where tax is collected and remitted. The table assumes that's every payment, adding $200 and $2,000.

The table also assumes tax is collected and remitted on every payment. That's the worst case for Whop's per-transaction tax fee and the best case for Stripe's flat Tax Complete fee. For a B2B SaaS, tax often applies to only 25 to 50% of payments (see Step 5). At 50%, Whop comes to $495 a month at $10k MRR and $4,950 at $100k MRR. At 25%, it's $445 and $4,450. Stripe stays at $525 and $5,260, and Paddle at $600 and $6,000, because their tax costs don't change with the share of taxed payments.

#### Which option fits your stage?

For a small team or new startup, an all-in-one platform is usually the quickest way to get checkout, billing, subscription access, and invoicing running from one dashboard. 

[Cal.com](https://whop.com/blog/cal-whop/) used Whop’s embedded checkout to launch payments in its booking flow in under two weeks. 

> We didn’t want our team spending months rebuilding infrastructure that already existed. 
> – Cal.com Co-founder Peer Richelsen

A merchant of record makes sense if you want a third party to act as the legal seller in every market you sell into, but make sure to check its coverage before you commit. 

If tax is collected on every payment, a processor stack works out cheaper, but the savings at $10k MRR aren't huge (about $70/month). If you're also paying for engineering resources, those savings may not cover it until you're closer to $100k MRR (saving about $690/month). If tax applies to half your payments or fewer, as is common in B2B, Whop comes out cheaper at both levels. 

Stuck between an MoR and a processor? Read our review of [Paddle vs Stripe](https://whop.com/blog/paddle-vs-stripe/).

### Step 3: Add checkout

You have options when it comes to checkout: links and hosted checkout, embedded checkout, and fully custom-built checkouts. 

Here are the key differences.

#### Hosted vs embedded vs custom checkout

<table style="table-layout: fixed; width: 100%;">
  <colgroup>
    <col style="width: 16%;">
    <col style="width: 21%;">
    <col style="width: 21%;">
    <col style="width: 21%;">
    <col style="width: 21%;">
  </colgroup>
  <thead>
    <tr>
      <th style="vertical-align: top;">Checkout</th>
      <th style="vertical-align: top;">Time and effort to ship</th>
      <th style="vertical-align: top;">Conversion</th>
      <th style="vertical-align: top;">Branding control</th>
      <th style="vertical-align: top;">PCI scope</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Hosted</strong></td>
      <td>Minutes: create a product and share the checkout link</td>
      <td>Customers leave your site to pay, but wallets and saved details work out of the box</td>
      <td>Your logo and colors on the provider's page</td>
      <td>Smallest: card data never touches your site</td>
    </tr>
    <tr>
      <td><strong>Embedded</strong></td>
      <td>Hours to days: add the checkout component to your app</td>
      <td>Customers pay without leaving your site</td>
      <td>Matches your site, within the component's styling options</td>
      <td>Small: card fields are isolated, but you must protect the page from malicious scripts</td>
    </tr>
    <tr>
      <td><strong>Fully custom</strong></td>
      <td>Weeks or more: you build and maintain every part of the flow</td>
      <td>Fully tailored, but you build wallets, retries, and local payment methods yourself</td>
      <td>Complete</td>
      <td>Largest: you handle card data and take on the full compliance burden</td>
    </tr>
  </tbody>
</table>

The simplest way to get started with checkout is to use a hosted solution through your payment provider. 

That way, you can start taking payments quickly, and switch to an embedded flow when keeping checkout inside your app starts to matter for conversion.

With Whop’s embedded checkout, [Nickel](https://whop.com/blog/nickel/) reported platform-wide payment completion rising from 29% to 47% over two months.

#### How to set up hosted checkout on Whop

To set up a hosted checkout with Whop, follow the steps below.

- Head to your business dashboard, click “Products”, and then click the blue “Create product” button.

![](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/images/2026/11/80.png)

- Within the editor, you can set a product title, description, and add videos and images. You can select "Generate with AI" to draft the name, page copy, pricing and apps, or fill it in yourself.

![](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/images/2026/11/81.png)

- Under Pricing, select “Paid access”, enter your amount, then click on the pricing option.

![](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/images/2026/11/82.png)

- In the next window, select “Recurring” from the dropdown, and pick the interval (for example, 1 month). You can also toggle on free trials and choose the length. Plan settings let you to set an optional initial fee, cancellation discount, and 3D Secure for payments.

![](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/images/2026/11/83.png)

- Toggle on “Customize payment methods” to choose which local methods appear. Some payment methods are not available for subscriptions; those will be grayed out. You can also select to automatically include new payment methods as they become available.

![](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/images/2026/11/84.png)

- Select “Done”, then “Create product”. Head back to the Products tab of your dashboard, and you'll see a button to copy your checkout link for each product you create.
- Add your checkout link to the subscribe or sign-up button on your pricing page. You can also share it directly in emails, social posts, or your app. When a customer pays through the link, Whop starts their subscription and grants access.
- **Optional:** You can also add a promo code. Scroll down the nav menu on the left side of your business dashboard, select "Promo codes", and then click "Create promo code". Here you can create your code and select the discount rate, eligible users, discount duration, and more. If you have multiple product links, you can apply the code to specific products only.

![](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/images/2026/11/Promo-code.png)

#### Developer route: embedded checkout with Whop Elements

![Video thumbnail](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/media/2026/11/whop-embedded-checkout_thumb.jpg)
[Watch video](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/media/2026/11/whop-embedded-checkout.mp4)

You can also embed Whop checkout directly into your website or app. Whop Elements works with React or plain JavaScript: pass your plan ID to the Checkout element, and it handles pricing, promo codes, currency, and payment. You can also add express checkout for Apple Pay, Google Pay, or PayPal. 

##### Here’s the React setup:

<div class="whop-code">
  <div class="whop-prompt-head">
    <div class="whop-prompt-title">checkout.tsx</div>
    <button class="whop-prompt-copy" type="button">Copy</button>
  </div>
  <div class="whop-code-body" style="max-height: none;">
    <code class="language-tsx">import { Checkout, CheckoutElement, WhopElements } from "@whop/elements-react";
import { loadWhop } from "@whop/elements";

export function CheckoutPage({ userId }: { userId: string }) {
  return (
    &lt;WhopElements elements={loadWhop()}&gt;
      &lt;Checkout
        plan="plan_xxxxxxxxxxxxx"
        metadata={{ user_id: userId }}
        returnUrl="https://yourapp.com/billing/return"
      &gt;
        &lt;CheckoutElement /&gt;
      &lt;/Checkout&gt;
    &lt;/WhopElements&gt;
  );
}</code>
  </div>
</div>

Check out our guides to [adding checkout to a Next.js app](https://whop.com/blog/add-checkout-to-nextjs-app/) and [building a subscription billing app](https://whop.com/blog/build-subscription-app/) with Next.js and Whop.

#### Checkout requirements checklist

For a smooth customer experience, make sure your checkout meets every item below:

- Accepts a mix of payment methods: cards, wallets, local methods (like iDEAL and ACH)
- Includes a field for coupon or promo codes
- Clearly shows plan tiers (if applicable)
- Shows the renewal price and date before payment
- Offers a free trial up front (if applicable), and explains when the trial ends and billing starts
- Shows a clear message if a payment fails, with a way to retry

![](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/images/2026/11/failed-payment-whop-checkout.png)

### Step 4: Set up the billing layer

Your billing layer takes over after checkout. An all-in-one platform or merchant of record includes one. With a processor stack, you [build or buy](https://whop.com/blog/choosing-the-right-saas-billing-solution-for-your-business/) the billing layer and connect it yourself.

> I would recommend planning out the exact flow that your users will use to manage their billing and account. Can they cancel their membership directly from your website, or do you want to send them to a hosted billing page on the payment provider’s website? 
> 
> – Colin McDermott, Whop Head of SEO/GEO

#### What your billing layer needs to manage

Your billing layer needs to be able to handle the following:

- Upgrades and downgrades, with proration
- Free trials that convert to paid plans
- Pauses and cancellations, at period end or immediately
- Payment retries and a grace period before access ends
- Automatic card updates when cards expire
- A self-service portal to update cards, view invoices, and cancel
- [Invoicing](https://whop.com/blog/best-invoicing-software/) for B2B buyers, including annual contracts

A solid failed payment flow is crucial. Nearly half of failed payments on monthly plans are never recovered, and on annual plans only 23% are, according to Recurly's 2026 State of Subscriptions report.

#### How failed payments work on Whop

When a renewal fails, the subscription moves to "Past due". Whop emails the customer to update their card and retries the charge over five days, then cancels the subscription if it still fails. You can also link customers to their billing portal from your app to update their card, and retry the payment manually from your dashboard.

**[How Whop handles payment declines](https://docs.whop.com/payments/payment-declines)**

Five days is a short recovery window, and a manual retry also only works while the subscription is still past due, so it has to happen inside those five days.

To reach customers who miss the reminder emails, show your own in-app banner linking to the billing portal from the first failed charge. 

If you need a longer retry schedule that you set yourself, a processor's billing tool like Stripe Billing gives you that control, at the cost of more setup.

#### Gating SaaS access with Whop

For products you sell and deliver on Whop, membership access updates automatically. 

If a renewal fails, the "Keep access while past due" toggle under "Settings" and "Checkout" determines whether customers can keep using the product while Whop retries the payment. 

Turn it on if most of your customers are businesses or on annual plans, so they aren't locked out mid-recovery.

![](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/images/2026/11/subscriptions.png)

If customers sign in to your own web app, create the checkout through the API with their app user ID in the metadata. 

When they pay, the `membership.activated` webhook returns that ID, so you can link the purchase to their account and save their Whop user ID. The event fires again on every renewal, so make sure your code can handle receiving it more than once.

Before serving paid features, your server calls `users.checkAccess` with the customer's Whop user ID and your product ID.

Whop tracks renewals, cancellations, and refunds, so your app can check whether someone has access at any given moment. For downloadable software, you can validate license keys through the API.

**[Selling software on Whop](https://docs.whop.com/supported-business-models/saas)**

### Step 5: Handle sales tax and VAT

Handling sales tax and VAT is the next step in setting up your payments as a SaaS company.

#### When you have to register and collect

If you sell from outside the EU or UK, your first $50 subscription to a consumer there can be enough to trigger VAT registration. 

HMRC sets no registration threshold for overseas sellers, and in the EU you can file VAT for every member state through a single One Stop Shop (OSS) registration.

In the US, you collect tax in your own home state from your first sale (if the state taxes SaaS). In other states, you only collect once your sales there pass that state's threshold (and only if it taxes SaaS at all).

**Many US states use a $100,000 sales threshold:** South Dakota, whose law set the standard in the 2018 Wayfair ruling, uses $100,000 and dropped its old 200-transaction test in 2023, according to its Department of Revenue.

Here is how four states treat SaaS. 

- **Texas:** according to the Texas Comptroller, SaaS counts as a data processing service, and 20% of the charge is exempt, so tax applies to 80% of it.
- **Virginia:** generally doesn't tax SaaS. In a November 2024 ruling, the Virginia Tax Commissioner found that cloud-based software isn't taxable because customers don't receive any tangible property.
- **California:** doesn't currently tax SaaS, but the California Department of Tax and Fee Administration (CDTFA) says that from January 1, 2027, a new law (Senate Bill 122) makes prewritten SaaS taxable.
- **Oregon:** has no sales tax at all, so SaaS sales there aren't taxed.

In Canada, non-resident sellers of digital services generally need to register for GST/HST when their sales to Canadian consumers exceed C$30,000 over any 12 months.

#### Who handles it under each option

As you can see, each new market you sell into can mean another set of rules to track, another registration, and another filing responsibility. 

And if you're launching internationally with a small team, that's a lot of admin to take on from day one. 

Choose a provider that can collect the tax, file the returns, and pay it to the tax authorities in the markets you plan to sell into.

A merchant of record remits your tax and handles the complexity for you, which takes a lot of the work off your plate as part of the cost.

Whop can calculate, collect, and remit your tax in US states and territories, the EU, and the UK, for 2% per transaction. 

You can also have Whop simply calculate and collect your tax at checkout for 0.5% per transaction, across all US states and in 90+ countries covered by Numeral. You handle registration, filing, and remittance.

With a payment processor, you stay responsible for tax, though you can add a tax tool to take on some of the work. 

Stripe, for example, offers Tax Basic, which calculates and collects tax at checkout for 0.5% per transaction (or $0.50 per transaction via the API), wherever you're registered. However, it leaves registration, filing, and remittance to you. 

Stripe Tax Complete can also handle registration and filing on your behalf in supported jurisdictions, at an additional cost (starting at $90/month, which covers 200 monthly transactions, 2 registrations per year, and 4 filings per year). 

#### What will my tax costs be?

How much your tax handling costs depends on how many of your payments actually carry tax. 

Stripe Tax Complete is a flat monthly fee on a one-year contract, whether you collect tax or not. Whop's 2% only applies to payments where tax is collected. For a B2B SaaS, that can be well under half of payments, since EU business customers account for their own VAT and many US states don't tax SaaS.

<table style="table-layout: fixed; width: 100%;">
  <colgroup>
    <col style="width: 34%;">
    <col style="width: 33%;">
    <col style="width: 33%;">
  </colgroup>
  <thead>
    <tr>
      <th style="vertical-align: top;">Payments with tax collected</th>
      <th style="vertical-align: top;">Stripe Tax Complete</th>
      <th style="vertical-align: top;">Whop (collects and remits)</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>$10k MRR, 25%</strong></td>
      <td>$90/month</td>
      <td>$50/month</td>
    </tr>
    <tr>
      <td><strong>$10k MRR, 50%</strong></td>
      <td>$90/month</td>
      <td>$100/month</td>
    </tr>
    <tr>
      <td><strong>$10k MRR, 100%</strong></td>
      <td>$90/month</td>
      <td>$200/month</td>
    </tr>
    <tr>
      <td><strong>$100k MRR, 25%</strong></td>
      <td>$910/month</td>
      <td>$500/month</td>
    </tr>
    <tr>
      <td><strong>$100k MRR, 50%</strong></td>
      <td>$910/month</td>
      <td>$1,000/month</td>
    </tr>
    <tr>
      <td><strong>$100k MRR, 100%</strong></td>
      <td>$910/month</td>
      <td>$2,000/month</td>
    </tr>
  </tbody>
</table>

**Tax coverage differs:** Stripe’s plans cap registrations and filings, Whop remits in the US, EU, and UK, and Paddle is the seller of record worldwide.

### Step 6: Test before you go live

Before you launch, test what happens when a customer subscribes, renews, changes plans, or cancels.

#### The easiest ways to test

On Whop, you can create a separate account at [sandbox.whop.com](https://sandbox.whop.com/) and set up a test product, subscription plan, and checkout link. 

If your app uses the API or webhooks, create sandbox API keys and configure a test webhook there too. Whop provides test card numbers for successful payments, declines, and 3D Secure, so you can try each scenario without a real card.

Once you go live, make one real purchase and refund it to confirm everything works with real payments.

If your provider offers a sandbox or test mode, use it to run through similar scenarios without charging a real card.

![Screenshot of issuing a test refund within the Whop sandbox.](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/images/2026/11/refund-sandbox.png)

#### Pre-launch test checklist

Before you launch, work through the list below and compare what the customer sees with what your billing dashboard records.

- **Checkout:** use test cards to run a successful payment, a decline, and a 3D Secure challenge.
- **Trials:** start a trial and verify the date and amount of the first paid charge.
- **Plan changes:** if your provider supports mid-cycle upgrades and downgrades, check any prorated charges or credits.
- **Cancellation:** confirm the webhook updates app access when the subscription ends.
- **Failed renewal:** use a card that pays the first time but declines later charges (on Whop’s sandbox, use card no. 4000 0000 0000 0341). Then check that the customer gets a payment recovery email with a link to update their card.
- **Refunds:** issue a refund and verify the amount and status.
- **Tax:** check the tax charged in two jurisdictions you plan to sell into.
- **Invoices:** verify the customer details, line items, tax, and total.

#### Fraud and chargeback readiness

To mitigate [chargebacks](https://whop.com/blog/chargebacks/) and fraudulent activity, turn on 3D Secure so the customer's bank verifies risky payments, use a statement descriptor customers will recognize, and show your refund policy at checkout. 

On Whop, Radar screens payments for fraud automatically, and you can turn on [3D Secure](https://whop.com/blog/whop-3d-secure/) under "Settings" then "Risk". 

Early dispute alerts refund payments under your limit before they become disputes, so they don’t count against your dispute rate. Each alert costs $29, more than the $15 dispute fee on a typical subscription, so it’s mainly worth it to keep your dispute rate low.

Dispute Fighter builds your case for 15% of any dispute it wins.

### Step 7: Go live and monitor

With [payment acceptance](https://whop.com/blog/payment-acceptance/), billing, tax, access, and fraud now handled, it's time to go live. From here, it's important to start monitoring certain metrics to see how your product sales are trending.

#### Metrics to watch in the first 30 days

- **Checkout conversion:** Track how many checkout visits turn into purchases
- **Card authorization and involuntary churn:** Track the share of card attempts approved and how many subscriptions end after failed renewals
- **Refund and dispute rates:** Visa flags merchants as “excessive” once fraud reports and disputes reach 1.5% of transactions, and at least 1,500 a month. Mastercard’s threshold is 1.5% with at least 100 chargebacks a month. Your [Payment health dashboard](https://docs.whop.com/trust-and-safety/account-health/payment-health) on Whop shows your dispute rate against that 1.5% line, alongside your refund rate.

The Analytics tab in your Whop dashboard shows you total visitors, traffic over time, profit, gross transaction value by period, average spend per customer, top sources (when connected to your app or website), trial conversion rates, devices, countries, and more. 

You can customize your Analytics by adding and removing the exact charts you want.

![](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/images/2026/11/analytics.png)

You can also download cashflow reports with money in, money out, deposits, withdrawals, and starting and ending balances for your desired period. 

#### Signs your payment setup isn't working

After a few billing cycles, look at where you're losing customers and what your team still has to fix by hand.

A few issues worth taking note of:

- Customers abandon checkout when their payment method or currency is missing
- Renewals go unpaid even after retries and card updates
- You spend hours each month correcting invoices, tax, or subscription access
- Disputes are approaching card network thresholds
- Your provider can't support the per-seat or usage-based pricing you want to introduce

Fulfillment platform [ecomflow](https://whop.com/blog/ecomflow/) used to have client payments arriving without clear references, which had to be matched to invoices by hand. 

After switching to Whop, each payment carries its invoice ID, so it’s matched automatically. 

> We really switched from a sheets-based, manual-operations business. 
> 
> – ecomflow CTO Nolan Rook

Before changing providers, check whether you can move saved payment methods along with your subscriptions. 

[Whop Migrations](https://whop.com/blog/migrations/) transfers eligible Stripe subscriptions and their payment tokens together, so customers renew on their usual date without re-entering their card details. 

You can preview which subscriptions qualify before you confirm the migration.

## Top payment processing providers for SaaS

The model you choose in Step 2 determines how much you'll need to set up yourself, from creating your checkout to managing subscription access and tax responsibility. 

Here’s how five [SaaS payment](https://whop.com/blog/the-best-saas-payment-gateways/) providers stack up:

<table style="table-layout: fixed; width: 100%;">
  <colgroup>
    <col style="width: 20%;">
    <col style="width: 26%;">
    <col style="width: 28%;">
    <col style="width: 26%;">
  </colgroup>
  <thead>
    <tr>
      <th style="vertical-align: top;">Provider</th>
      <th style="vertical-align: top;">Published fee</th>
      <th style="vertical-align: top;">Built in</th>
      <th style="vertical-align: top;">Best for</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Whop</strong><br>All-in-one</td>
      <td>2.7% + $0.30; Billing +0.5% per transaction; Whop Tax Service from 0.5% per transaction</td>
      <td>Checkout, billing, access gating, invoicing, payouts, optional tax</td>
      <td>Launching from the dashboard, scaling on the API</td>
    </tr>
    <tr>
      <td><strong>Stripe</strong><br>Processor</td>
      <td>2.9% + $0.30; Billing +0.7% per transaction; Tax Basic from 0.5% per transaction</td>
      <td>Billing (with access entitlements) and tax as paid add-ons</td>
      <td>Teams with an engineer who want full control</td>
    </tr>
    <tr>
      <td><strong>Adyen</strong><br>Processor</td>
      <td>$0.13 + interchange + 0.60% (Visa/Mastercard)</td>
      <td>Card tokens and card updates; billing and tax separate</td>
      <td>High-volume SaaS with a payments team</td>
    </tr>
    <tr>
      <td><strong>Paddle</strong><br>Merchant of record</td>
      <td>5% + $0.50, all-in</td>
      <td>Billing, tax, chargebacks</td>
      <td>B2B SaaS that wants a global legal seller</td>
    </tr>
    <tr>
      <td><strong>FastSpring</strong><br>Merchant of record</td>
      <td>Quote-based</td>
      <td>Billing, tax, fraud tools, B2B invoicing</td>
      <td>Software sold mostly internationally</td>
    </tr>
  </tbody>
</table>

### 1. Whop

***Best for:*** *teams that want to launch their whole SaaS payments flow from the dashboard and use the API as their business expands.*

Whop is an all-in-one platform that covers checkout, subscription billing, and access, with built-in fraud screening and optional tools for tax handling, 3D Secure, and payment orchestration. 

You can build a website using [Whop blueprints](https://whop.com/blog/whop-blueprints/) or [migrate your existing website](https://whop.com/blog/website-migrations/) over to Whop, and configure checkout, monitor analytics, and distribute ads from the same dashboard. 

With [Whop Levels](https://whop.com/blog/whop-levels/), you gain access to lower processing rates as your spend on Whop Cards, Ads, and Investing grows.

### 2. Stripe

***Best for:*** *teams that have an engineer to handle the dev work and want control over how checkout, billing, and subscription access fit into their product.*

Stripe is a payment processor with paid add-ons for subscription billing and tax. You can start with a hosted Payment Link and give subscribers a self-service portal to update their card, switch plans, or cancel.

If your pricing tiers unlock different features, Stripe Entitlements (a feature within Stripe Billing) lets you map features to each product. Your app then uses those entitlements to decide what each customer can access.

### 3. Adyen

***Best for:*** *high-volume SaaS businesses with a payments team and a billing system they want to keep.* 

[Adyen](https://whop.com/blog/adyen-payments/) is a processor for businesses that need to accept payments across multiple markets. It saves cards as tokens for recurring charges, and can refresh card details when a card expires or is replaced.

Your billing system decides when a subscription renews and how much to charge, then sends Adyen the payment request. That lets you keep your existing billing logic in place as you add local payment methods or expand into new markets.

A minimum invoice may apply depending on your industry.

Check out our head-to-head of [Adyen vs Stripe](https://whop.com/blog/ayden-vs-stripe/) to weigh up the features and costs of both processors.

### 4. Paddle

***Best for:*** *B2B SaaS teams that want a third party to act as the legal seller across the markets they serve.*

[Paddle](https://whop.com/blog/what-is-paddle/) is a merchant of record built for SaaS. If you sell annual contracts, for example, you can invoice a buyer through Paddle and use the same subscription events to manage access in your app when the contract renews or ends.

Before going live, you can use Paddle's sandbox to check how your app responds when a subscription changes.

Buyers can manage their subscriptions through a customer portal, and Paddle offers automated dunning and churn prevention tools to help increase retention.

### 5. FastSpring

***Best for:*** *teams with a large share of international sales who want sales taxes collected and remitted automatically.*

FastSpring is another merchant of record for software businesses selling internationally. It can show buyers local currencies and payment methods at checkout, then converts payments into your base currency.

If you sell downloadable software, you can set FastSpring to deliver a download or license key after purchase. For a web app, use subscription events to keep access current.

Customers can manage subscriptions through a self-service portal, with FastSpring allowing users to switch their plans mid-cycle while it handles proration.

## Run your whole SaaS payment flow with Whop

To get payment processing for your SaaS running, follow steps 1 to 7: choose your billing model and provider, set up checkout and subscriptions, sort out tax, test and go live. 

The biggest decision is how much of that setup you want to build and maintain yourself.

With Whop, you can host your site, set up checkout, and manage [recurring billing](https://whop.com/blog/recurring-billing-for-saas/), customer invoices, subscription access, and payouts from one dashboard. 

You can also opt in to tax calculation and collection for 0.5% per transaction (only on payments where tax is collected), or 2% per transaction to add remittance (in supported markets). 

Start with a hosted checkout link, then embed checkout and use the API as you scale.

**[Sell with Whop](https://whop.com/network/)**

---

## SaaS payment processing FAQs

### How do I accept online payments for my SaaS product?

Accepting online payments for SaaS requires a payment provider that can support recurring billing flows, like Whop, Stripe, or Paddle. You'll need to create a product and set its recurring price and billing frequency, add a hosted checkout link to your website (or embed a checkout using an API), and make sure your billing provider can monitor and update product access depending on your customer's subscription status.

### What payment setup should a SaaS startup use?

Most SaaS startups should start with hosted checkout through an all-in-one platform like Whop, or a merchant of record provider that caters to SaaS. Look for recurring billing, a way to manage subscription access, and tax coverage in the markets you sell into. 

### Do I need to charge sales tax or VAT on SaaS subscriptions?

Yes, you'll need to collect sales tax and VAT where SaaS is taxable and you meet the local requirements. Many US states apply a sales threshold to out-of-state sellers. If you sell from outside the EU, VAT generally applies from your first taxable sale to an EU consumer. A merchant of record collects and remits tax as the legal seller, while an all-in-one platform like Whop offers optional calculation, collection, and remittance in supported markets. If you handle tax yourself, you're responsible for registration, filing, and remittance.

### How do I handle failed payments and churn from expired cards?

Look for a provider that has a system in place for payment retries. Give customers a short period to fix their payment details, and send an email or an in-app prompt. Whop emails your customers prompting them to update their payment info, and automatically retries the charge over a 5-day period. If the payment still fails after 5 days, Whop automatically cancels the subscription.
