Crypto Subscriptions Without Chargebacks: Keep Renewals Collected

Why a $29 renewal is the riskiest charge you process

A subscription is the one business model where you charge someone who is not in the room. Each renewal is a payment made weeks after the customer last thought about you. Card rails handle that gap badly.

The first problem is the dispute. A subscriber scans a statement, sees a descriptor they do not recognize and calls the bank instead of your support inbox. The issuer can look back over several renewals, so one call can reverse a whole billing history. You lose the revenue and never get the chance to simply cancel the plan.

The second problem is quieter and usually larger. The customer still wants the product, but the stored card stopped working. Cards expire, banks reissue them after a breach, and issuers decline foreign recurring charges. Baremetrics, citing Paddle research, reports that involuntary churn makes up 20% to 40% of total churn, and that it costs the average subscription company about 9% of monthly recurring revenue.

The third problem is how your acquirer sees you. In its 2026 notice, the Merchant Risk Council confirms that Visa cut the merchant threshold in its VAMP program from 2.2% to 1.5% on April 1, 2026. The ratio is fraud reports plus disputes, divided by settled card-not-present transactions. Subscriptions sit in that denominator every month.

A 1,000-subscriber business, priced out

Take a SaaS tool with 1,000 subscribers at $29 a month. That is $29,000 of MRR and $348,000 a year. The table uses the sourced figures above and two assumptions that are labelled as such.

Baremetrics measured it across its own customer base, so your number will differ. The next two rows show the mechanism, not a forecast. A founder with 1,000 subscribers can lose a fifth of the base to expired cards without ever hearing a complaint.

The dispute row needs a caveat. Visa applies its Excessive label only above a minimum monthly case count, and sources disagree on that floor. A business this size may never be labelled. It still pays a fee on each dispute and carries the evidence work for a charge it will probably lose.

For comparison, the Payzum fee on this volume is one fixed percentage. A customer who pays 100 means the merchant receives 99.50. A $29 plan lands as $28.855 before gas, and no renewal can be pulled back later.

Where card billing breaks for recurring revenue

Four design choices in the rails explain all of this, whichever processor you use.

Reversibility comes first. The cardholder's promise is an undo button, and the merchant answers a dispute with proof of delivery. A subscription delivers access, not a parcel, so the tracking number that wins disputes does not exist.

Renewals depend on a credential that decays. Card-on-file billing stores a token for a card with an expiry date, an issuing bank and a replacement cycle. You control none of those. Account updaters and smart retries soften the damage but cannot remove the dependency.

The issuer decides every month. A renewal is a request that a risk model approves or declines, and recurring foreign charges draw suspicion by default. That is twelve approval decisions per customer per year.

Custody creates the reserve. Money that passes through an acquirer's balance is briefly their liability, which is why holds and rolling reserves exist. Remove the balance and the reserve has nothing to attach to.

Rules that still apply when the card is gone

Dropping chargebacks does not drop consumer-protection law. In the United States, ROSCA still requires sellers of online subscriptions to disclose material terms clearly before taking billing information, get express informed consent and provide a simple way to stop recurring charges, according to Gibson Dunn's review of the rule.

The FTC's broader click-to-cancel rule was vacated by the Eighth Circuit in July 2025. The agency has since restarted rulemaking, and the same law firm notes that ROSCA enforcement continues in the meantime. Many states also have their own automatic-renewal laws.

Show the price and cycle before payment, make cancellation easy and keep a record of consent. A different rail moves the payment risk, but the disclosure duties stay with you. Confirm the specifics with your own counsel.

How Payzum bills a subscription without a card on file

Payzum is a non-custodial, crypto-only payment processor. When a subscriber pays, funds route straight to a wallet you control. Payzum never pools or holds the money, so there is no balance to reserve against and no intermediary re-underwriting you mid-cycle. The mechanic is the one in non-custodial crypto payment processing, applied to recurring revenue.

Recurring subscriptions sit beside hosted checkout, payment links and invoices. You define the plan and the subscriber pays each cycle from their own wallet. Each payment settles on-chain. Two questions that dominate card billing stop applying: will this renewal be reversed, and is this credential still alive?

The failure mode changes shape. On cards, a subscription dies silently when a credential decays. On-chain, it lapses visibly when a subscriber does not renew. That is a retention conversation instead of a payments bug, and signed webhooks fire on confirmed payments so your app, Discord bot, course platform or door system can grant and revoke access on its own.

Auto-convert settles every cycle as USDC or USDT whatever the subscriber sent, so a $29 plan is $29 in stablecoins. USDC is issued fully reserved against dollar-denominated assets, which is what lets it work as a price unit and not just a settlement token.

The rest of the lifecycle runs on the same account. Hosted checkout (redirect, modal or inline) and no-code payment links handle signup. Invoices with expiration and overpayment detection handle annual plans and retainers. The POS serves members who pay at a counter, with a fresh QR per payment and PIN cashiers. Mass payouts, as CSV batches in BTC, LTC or DOGE or as EVM stablecoin payouts on Polygon, Arbitrum, Optimism, Base, BNB Chain and Avalanche, pay the affiliates funded by that MRR. The pattern is covered in crypto mass payouts.

Underneath sits ordinary infrastructure: a REST API with API keys, signed webhooks, 2FA, encrypted secrets and an audit log. Payzum settles across nine networks: Bitcoin, Ethereum, Solana, Polygon, Base, Arbitrum, Optimism, BNB Chain and Avalanche. Confirmation takes about 0.4 s on Solana and about 2 s on Base and Polygon. If your product is an API, the same account can make it payable per call over x402.

Setting up your first plan in four steps

1. Create a Payzum account and connect a wallet you control, such as a hardware wallet for a solo operator or a multisig for a company. There is no acquirer application and no reserve to negotiate. Switch on auto-convert so each cycle lands as USDC or USDT.
2. Define the plans. Set monthly and annual tiers in stablecoin terms and pick the chains you accept. Make an invoice template for annual and enterprise deals, so one plan can be sold either way.
3. Put signup where customers already are. Drop hosted checkout into your pricing page, or publish a payment link for email, chat and sales calls. Existing plugins keep working, because this is a path you add and not a stack you migrate.
4. Wire access to webhooks and go live. A confirmed payment provisions the account, adds the role or extends the licence, and a lapsed cycle downgrades it. For members at a counter, open the POS on a phone. When affiliates need paying, upload one CSV.

Who bills this way: eight subscription models

• SaaS and developer tools. Monthly and annual plans in USDC, with webhooks provisioning seats and licence keys. Customers abroad pay the same way as customers at home. See accepting USDC payments in a SaaS.
• Paid communities and memberships. The subscription is the access, so the webhook that confirms payment also adds the role. A member cannot use three months of a community and then claw the money back.
• Gyms, studios and clubs. Online signup uses hosted checkout, and the front desk uses a QR, with a PIN cashier per staff member so takings reconcile separately. The flow is in accepting USDC payments in a gym.
• Course creators and cohort programs. Monthly library access or instalments on a high-ticket cohort, each final on payment. See crypto payments for online courses.
• Creators, newsletters and sponsorware. Small supporter tiers stay worthwhile because moving a stablecoin costs little and no platform takes a second cut. See accepting crypto donations.
• Agencies and consultants on retainer. A recurring plan for the monthly fee, plus expiring invoices for project work. See crypto payments for a digital agency.
• Hosting, VPN and infrastructure providers. Customers who chose you for privacy pay without handing a card number to a chain of intermediaries. API products can add an x402 per-call option.
• Marketplaces with seller plans. Seller subscriptions come in and stablecoin payouts go out, both non-custodial.

Card renewals and crypto renewals, row by row

If you are choosing between crypto providers, the Payzum comparison pages set out how the custody models differ.

Objections from subscription founders

Without a card on file, is every renewal a chance to churn?

Yes, and it is a visible one. Card billing hides churn, then turns a share of happy customers into involuntary churn and adds a dunning workflow to win them back. On-chain, a subscriber who wants the product renews and a subscriber who does not lapses. You still run retention with reminders, annual discounts and usage nudges, but against real intent and not an expired number. Selling annual plans works here as it does on cards: twelve months collected on-chain are yours from day one.

My subscribers pay by card today. Can I migrate them?

Keep your card billing. Payzum is crypto-only and does not settle to a bank account, so it works as a second rail beside your fiat stack. It earns its place where cards are weakest: customers abroad, crypto-native users, high-ticket plans where one dispute hurts and any segment that makes your acquirer nervous. Adding it costs a page and a webhook.

Is my money safe if Payzum never holds it?

There is no pooled balance to freeze or reserve against, which removes the risks subscription businesses usually meet. The trade-off is that you hold the keys. Use a hardware wallet for a solo operator and a multisig for a company treasury. The account itself has 2FA, signed webhooks, encrypted secrets and an audit log.

What about price moves between cycles?

Turn on auto-convert. Each cycle settles as USDC or USDT whatever the subscriber sent, so a $49 plan is $49 in stablecoins each month.

How do I handle accounting?

Each cycle leaves an on-chain record plus the transaction history and audit log in your account, which is what your bookkeeper reconciles against. Treatment depends on jurisdiction. In the United States the IRS treats digital assets as property rather than currency, which affects how each receipt is valued. Confirm the specifics with your accountant.

Before you add the rail: a six-point checklist

• Pull your last 12 months of failed renewals and disputes, and count how many were involuntary.
• Pick the segment that gets the crypto option first, such as foreign customers or annual plans.
• Decide who holds the keys to the receiving wallet, and where the backup lives.
• Write the cancellation and refund policy, and show it before payment.
• Point signed webhooks at your entitlement system and test a lapsed cycle.
• Ask your accountant how each stablecoin receipt will be recorded.