Can a SaaS accept only stablecoins? Who it works for, and the risks

Payzum is a non-custodial, stablecoin-first crypto payment processor: payments settle directly to wallets the merchant controls. That one fact shapes this whole question. A founder who asks "can we take only stablecoins?" is really asking whether the people who pay them are willing and able to send USDC or USDT. The software side is the easy part.

The question behind "stablecoins only" for a software business

The idea shows up often. A founder is tired of a card processor that declines foreign cards, holds a balance, or refuses the account. Another sells mostly to developers who already keep USDC in a wallet. A third has customers in countries where cards are rare. Each one wonders whether the cleanest move is to drop cards altogether.

Stablecoin-only can work. It can also fail quietly, because nobody emails you to say they left at checkout. You see only the signups that never happened.

So treat the choice as a sales decision first. The payment rail changes who can say yes. Before anything else, write down your last fifty paying customers and how each of them would pay if cards vanished tomorrow.

What your customers' own finance teams do today

In September 2026 the Cleveland Fed published Economic Commentary 2026-22. The authors asked 148 firms in the Fourth Federal Reserve District about stablecoins during September 18 to 25, 2025. One firm used them. Seven more planned to. The rest had no plans, did not know the technology, or were undecided.

Of the 102 firms asked about the barriers, 50 said they would need to see demand from their own customers, and 49 wanted to watch the market first. Another 42 wanted proof that stablecoins are cheaper or more efficient, 32 wanted clearer accounting and tax rules, and 30 said they would act if suppliers asked.

Read that from the seller's side. Your B2B buyer is often one of those firms. If you sell to them and say "stablecoins only," you become the supplier who asks them to change how they pay. The survey is regional and small, so do not stretch it into a national number. It is still a useful warning about mid-sized U.S. companies.

The failure you will not see in your dashboard

Cards fail loudly: a decline code, a dispute, a dunning email. A missing card option fails silently. The visitor reads your pricing page, finds no way to pay with the card in their pocket, and closes the tab.

• Buyers who use a company card cannot send USDC without finance approval, and finance may not have a wallet at all.
• Trials that ask for a card convert well. A trial that asks for a wallet transfer converts to a different, smaller crowd.
• Procurement teams often need a vendor form and a PDF invoice before they pay anyone.
• Customers who have never used a wallet need a guide for the first payment, and each guide is a support load.

Cards also fail for you, and that is why the stablecoin idea is tempting. Paddle's delinquent churn help page says failed payments can account for up to 40% of a SaaS company's churn. It adds that cards expire every three years, so about a third of customers must update their card each year. Those losses are real. The question is whether removing cards trades them for bigger ones.

A decision table: who can run on stablecoins alone

Use this table with your own customer list. A row where most of your buyers sit tells you more than any average.

If your customers fall in the top two rows, stablecoin-only is a sensible start. If they fall in the bottom two, keep a card route and treat stablecoins as an extra door.

A $16,000 MRR example: how few lost customers cancel the saving

Take a SaaS with 400 customers on a $40 monthly plan. Monthly recurring revenue is $16,000. Assume a card setup costs about 3% all in. That is an assumption, so swap in your own rate.

Read the last row twice. If going stablecoin-only costs you ten customers out of 400, the saving is gone. If it costs you forty, you are down $1,200 a month before counting the cost of acquiring them. Payzum's 0.5% is cheap, but it does not pay for lost sales.

The same arithmetic can point the other way. If half your pipeline cannot pay by card at all, a stablecoin link adds customers instead of removing them, and the saving is a bonus.

How a stablecoin-only checkout runs, step by step

If your buyers fit, the setup is short. Payzum offers invoices, payment links, a hosted checkout and recurring subscriptions, plus a REST API for custom flows.

1. Create your account, complete verification and add the wallet that will receive funds. You keep control of that wallet.
2. Choose the coins and networks you accept. Pick networks with cheap gas, such as Base, Polygon or Solana, so a $40 plan is not eaten by fees.
3. Connect billing. Use the hosted checkout or a payment link on your pricing page, or install a ready plugin if your billing sits on a supported platform.
4. Unlock access from the signed webhook, never from the page the customer returns to. The webhook proves the payment confirmed.
5. For each renewal, issue an invoice or link with an expiry date, and send a reminder before it lapses.
6. Export the ledger for your accountant each month. Payzum values every event in your reporting currency using the ECB reference rate for that day.

Payzum charges 0.5% per processed sale, deducted from the amount received, plus on-chain gas. A customer who pays 40 USDC leaves 39.80 USDC in your wallet, minus the small gas cost.

The risks founders raise, and the fix for each

Customer friction at checkout

Paying from a wallet takes more steps than typing a card number. Shorten it. Show the exact amount, the network and a QR code on one page, and add a short "how to pay with USDC" guide next to the button. Our guide on getting paid when Stripe is not available covers the same checkout from the seller's side.

Renewals without a card on file

This is the largest change. Do not assume the card-on-file style of automatic charging. Stripe's own stablecoin subscription guide, which was in preview with an access request when we checked on November 4, 2026, says the customer must authorize you to use their crypto wallet for future payments. That is a wallet permission, and not every customer will grant it. With Payzum, plan each renewal as a payment the customer completes. Annual plans suit this best, because the customer acts once a year. Our post on crypto subscriptions without chargebacks goes deeper on the billing side.

Records for your accountant

Every payment still needs an entry in your books. Payzum turns each sale, conversion, fee and payout into a ledger line, and the accounting exports work with QuickBooks, Xero and others. It gives you records, not tax advice. Your accountant decides the treatment.

Refunds

Nobody can pull an on-chain payment back, so a refund is a new payment you send. Write a refund policy and keep it short.

Three SaaS products, three different answers

An API tool for developers

Picture a logging API that sells a $30 plan and an annual plan to solo developers and small startups. Most buyers are on crypto-friendly forums, and many already hold USDC. Stablecoin-only is reasonable here. Offer a discount on the annual plan so the customer acts once a year, and let the signed webhook unlock the account.

A project tool for small agencies in Latin America

Picture a Buenos Aires team that sells a project tool to agencies whose cards fail on foreign recurring charges. Stablecoins are the way many of them already move money. A stablecoin link may bring in customers the card route never reached. Keep a card option for the agencies that have one, and treat the link as the main door.

An HR platform for mid-sized companies

Picture an HR tool that bills 200 employee seats through the finance team, which pays by purchase order. Stablecoin-only would shut that door. Keep cards or bank transfer as the default and offer a stablecoin invoice to the few customers who ask. The Cleveland Fed responses suggest that the ask is still rare in this segment.

For a full walk-through of the SaaS billing setup, see our guide to accepting USDC payments for a SaaS.

Stablecoin-only versus hybrid, side by side

A one-month test before you drop cards

You do not have to decide in the abstract. Run this checklist for a month.

1. Add a stablecoin payment link beside your card button. Leave cards on.
2. Tag every signup by how it paid, so you can compare conversion and churn by rail.
3. Ask new customers one question: "Would you have paid if only stablecoins were available?"
4. Count the share who say no. If it is under 2.5% of your base, the break-even row above says you can go further.
5. Check that your accountant is happy with the monthly export.

If most answers say no, you have your decision without losing a single sale.

Objections that come up on the first call

Is my money safe if I take no cards?

Payzum never holds your funds, so there is no processor balance to freeze. The risk that remains is yours to manage: the wallet and the stablecoin issuer. Use a wallet with proper key backup, and read the issuer's reserve reports.

Doesn't a stablecoin-only page look odd to a buyer?

It depends on the audience. To a developer it looks normal. To a procurement manager it looks like a gap. That is why the table above starts with your buyer.