Key Takeaways
- The global recurring payments market reaches $15.8 trillion in 2026 according to Juniper Research, yet nearly all of it still runs on traditional banking rails (credit cards, ACH). Recurring crypto payments remain a niche despite growing demand.
- Superfluid has processed over $650 million in cumulative streamed flows since launch (source: DefiLlama), making it the leading protocol for real-time payment streaming on Polygon, Arbitrum, and Base.
- Stablecoin transactions account for 70% of on-chain volume in 2026 according to Chainalysis, and Circle reports over $60 billion of USDC in circulation as of Q1 2025 — stablecoins have become the essential technical foundation for any viable crypto subscription.
- 562 million crypto holders worldwide in 2024 (Triple-A), representing 6.8% of the global population: the addressable market exists, but on-chain recurring payment tools still need to mature in reliability and regulatory compliance, including under frameworks like MiCA in the EU and evolving SEC/FinCEN guidance in the US.
- EIP-1337 and ERC-20 token approvals form the technical building blocks for subscription smart contracts, but their limitations — unpredictable gas fees, failed transactions, no native pull mechanism — continue to hold back large-scale adoption.
Why Recurring Crypto Payments Are Still a Hard Problem
Automatic billing, the kind you're used to with a Visa card or ACH debit, relies on a simple principle: the merchant pulls funds from the customer's account at regular intervals. This pull model works because banks act as trusted intermediaries, authorized to debit an account on the creditor's behalf.
On a blockchain, this mechanism doesn't exist natively. An Ethereum, Polygon, or Arbitrum wallet can't be debited by a third party unless the owner actively signs each transaction. That's a fundamental property of self-custody: nobody touches your funds without your private key. As a result, recurring crypto payments require technical workarounds — token approvals, dedicated smart contracts, continuous streaming — that add complexity exactly where users expect simplicity.
According to Juniper Research, the global recurring payments market reaches $15.8 trillion in 2026. Almost all of that money flows through traditional banking rails. The 562 million crypto holders identified by Triple-A in 2024 represent a massive pool of potential customers, but converting that base into on-chain paying subscribers means solving three problems at once: user experience, technical reliability, and regulatory compliance.
How On-Chain Crypto Subscriptions Actually Work
Pull vs. Push: The Fundamental Difference from Credit Card Billing
With a credit card, the merchant sends a charge request to the card network (Visa, Mastercard), which pulls funds from the customer's account. The customer authorizes once, and the merchant charges every month. That's the pull model.
On blockchain, the default model is push: the payer initiates every transfer. To simulate automatic billing, the payer must grant prior authorization to a smart contract, which can then transfer ERC-20 tokens on their behalf. This authorization is called a token approval.
The difference has real consequences. In the push model, a monthly subscription requires the customer to come back and sign a transaction every month — or delegate that ability to a smart contract. In the on-chain pull model, the subscription smart contract can execute the charge automatically, but only within the limits of the approval granted.
Token Approvals and Subscription Smart Contracts
The standard mechanism relies on the approve() function in the ERC-20 standard. The customer authorizes a smart contract to spend a defined amount of their tokens — say, 50 USDC per month. The subscription contract, triggered by a keeper (an on-chain bot) or by the merchant themselves, then calls transferFrom() to pull funds at each billing cycle.
EIP-1337, proposed back in 2018, aimed to standardize this process by defining an on-chain subscription format: amount, frequency, token used, recipient address. This standard was never formally adopted into core Ethereum, but its principles show up in most current crypto subscription protocols.
The main risk with token approvals lies in unlimited approvals. If a user approves an infinite amount (a common practice to avoid re-signing for each transaction), a compromised smart contract could drain their entire balance. Modern wallets like MetaMask and Rabby now flag this risk and offer capped approvals.
Protocols and Solutions Available in 2026
Superfluid: Real-Time Payment Streaming
Superfluid takes a radically different approach to recurring payments. Instead of a one-time charge each month, the protocol creates a continuous stream of tokens between the payer and the recipient. A $30/month subscription translates to a transfer of roughly $0.000011 USDC per second, continuously, with no individual transaction at each billing cycle.
According to DefiLlama data, Superfluid has processed over $650 million in cumulative streamed flows since launch. The protocol operates on Polygon, Arbitrum, Base, Optimism, and several other EVM chains. Supported tokens include USDC (via wrapped "Super Tokens"), DAI, and ETH.
The streaming advantage: no recurring gas fees for each payment, no monthly transaction failures to manage, and billing granularity that's impossible in traditional finance. A customer who cancels mid-month pays only for the portion used, down to the cent.
The limitation: the user must maintain a sufficient balance in their wallet. If the balance drops to zero, the stream stops automatically, and a liquidation mechanism recovers a security deposit (buffer) to cover the final moments of the stream.
Sablier and Llamapay: Programmable Payments
Sablier focuses on programmable payments with configurable distribution curves — linear, exponential, or stepped. Originally designed for token vesting and crypto payroll, Sablier also adapts well to B2B subscriptions, particularly for consulting or development services billed on a continuous basis.
Llamapay, built by the DefiLlama team, targets recurring payroll for DAO contributors and crypto freelancers more specifically. The protocol supports payment configurations in stablecoins (USDC, USDT, DAI) on Ethereum, Arbitrum, Polygon, and several L2s. Its straightforward interface makes it a popular choice for decentralized teams that want to pay their members without going through a traditional payroll system.
Request Network also deserves a mention: the protocol focuses on decentralized invoicing and enables on-chain invoices that can trigger recurring payments through third-party integrations. Request is used by several DAO treasuries and web3 companies to manage their crypto accounting.
Centralized Solutions: Coinbase Commerce, NOWPayments, CoinGate
For merchants who prefer to avoid the complexity of smart contracts, centralized crypto payment gateways offer subscription functionality.
Coinbase Commerce lets merchants accept payments in USDC, BTC, ETH, and DAI, with settlement to the merchant's Coinbase account. The platform doesn't support native streaming yet, but offers recurring payment links that the customer validates manually at each billing cycle.
NOWPayments offers a more robust subscription API: the merchant configures a recurring plan, and NOWPayments sends a notification to the customer for each payment due. The system supports over 350 cryptocurrencies, with automatic conversion to stablecoin or fiat available. Fees of 0.5% per transaction make it one of the most competitive options.
CoinGate offers a similar model with support for over 70 cryptocurrencies, a WooCommerce plugin, and settlement in USD or fiat for merchants. CoinGate has processed over 4 million transactions since launch and operates under license in Lithuania, which also helps with MiCA compliance in the EU.
These centralized solutions sacrifice decentralization (custodial or semi-custodial model) in favor of user experience and regulatory compliance.
Stablecoins: The Missing Link for Crypto Subscriptions
A $9.99/month subscription can't fluctuate by 15% from one month to the next without becoming unmanageable — for both the merchant and the customer. Stablecoins solve this fundamental problem.
Circle reports over $60 billion of USDC in circulation as of Q1 2025. USDC has become the go-to stablecoin for programmable payments, thanks to its transparency (monthly reserve attestations by Deloitte), native availability on more than 15 blockchains, and integration into virtually every recurring payment protocol.
According to Chainalysis, stablecoin transactions represent 70% of on-chain volume in 2026. That figure signals a structural shift: stablecoins are no longer just a trading tool — they're the dominant payment infrastructure of the crypto ecosystem.
Tether's USDT remains the most widely used stablecoin by global volume, but its adoption for professional recurring payments is hampered by transparency concerns and regulatory positioning. In the US, stablecoin issuers face increasing scrutiny from Congress and agencies like the SEC and FinCEN, with proposed stablecoin legislation (such as the GENIUS Act and STABLE Act) expected to bring clearer rules. USDC's positioning as a compliance-forward stablecoin gives it an edge with US-based merchants and enterprises.
For a SaaS company that wants to bill customers in crypto, a USDC subscription on Polygon or Base offers the best trade-off in 2026 between price stability, transaction costs (< $0.01 per transfer on these L2s), and compatibility with streaming protocols like Superfluid.
Current Technical and Regulatory Limitations
Volatility, Gas Fees, and Failed Transactions
Even with stablecoins, several technical obstacles persist.
Gas fees on Ethereum mainnet make small-amount recurring payments economically absurd. A $5 USDC subscription with $3 in gas every billing cycle makes zero sense. Layer 2 networks (Polygon, Arbitrum, Base) have reduced these costs to a few cents, but they require the customer to have funds on the right network — an added friction point.
Failed transactions are a structural problem. If the customer's wallet doesn't have enough tokens or gas at billing time, the transaction simply fails. Unlike a credit card that can automatically retry, a subscription smart contract requires either an automated keeper (expensive) or manual intervention. Superfluid partially works around this with its liquidation buffer, but the risk of involuntary churn remains high.
Chain fragmentation complicates things further. A customer on Arbitrum can't pay a merchant on Polygon without going through a bridge — an extra step, an additional security risk, and added latency. Cross-chain protocols like Chainlink CCIP are making progress, but seamless interoperability is more of a 2027–2028 goal than a 2026 reality.
US Regulatory Landscape for Recurring Crypto Payments
In the United States, recurring crypto payments sit at the intersection of several regulatory frameworks, and the landscape is evolving rapidly.
The SEC continues to assert jurisdiction over certain crypto assets, and the classification of tokens used in subscription payments matters. If a token used for recurring billing is deemed a security, the implications for merchants and payment processors are significant. Stablecoins like USDC, which are generally not classified as securities, sidestep this issue.
FinCEN requires businesses that transmit money — including crypto — to register as Money Services Businesses (MSBs) and comply with Bank Secrecy Act (BSA) obligations, including Know Your Customer (KYC) and anti-money laundering (AML) requirements. Centralized payment gateways like Coinbase Commerce and NOWPayments handle this compliance on behalf of merchants, which is a major advantage.
At the state level, money transmitter licenses (MTLs) create a patchwork of requirements. A merchant accepting recurring crypto payments directly (without a licensed intermediary) may need to evaluate state-by-state licensing obligations — a significant barrier to entry.
For decentralized protocols like Superfluid or Sablier, the compliance question remains open. The SEC and CFTC have not issued definitive guidance on fully decentralized protocols, and the line between true decentralization and a centralized service with a decentralized wrapper is a point of ongoing regulatory debate. Merchants using DeFi protocols for billing should consult specialized legal counsel.
In the UK, the FCA regulates crypto-asset activities under the Financial Services and Markets Act 2000, and firms must be registered for AML compliance. The FCA has signaled increasing oversight of crypto payment services, making licensed intermediaries the safer route for UK-based merchants.
MiCA (Markets in Crypto-Assets), fully applicable in the EU since January 2025, adds another layer for merchants serving European customers, requiring Crypto-Asset Service Provider (CASP) licensing and imposing specific requirements on stablecoin issuers.
Real-World Use Cases: SaaS, Media, DePIN
Crypto-native SaaS. Tools built for DAOs and web3 teams — treasury management, on-chain analytics, node infrastructure — are natural fits for USDC subscriptions. Platforms like Dune Analytics and Alchemy already offer crypto payment tiers, and recurring payments via Superfluid enable exact pro-rata billing based on actual usage.
Media and creators. The crypto version of Patreon already exists through platforms like Unlock Protocol, which uses subscription NFTs (membership NFTs) as access keys. The creator deploys a smart contract, the supporter mints a subscription NFT that expires on a set date, and renewal can be automated via a token approval. It's a hybrid model between recurring subscription and tokenized access.
DePIN (Decentralized Physical Infrastructure Networks). Networks like Helium, Hivemapper, and io.net bill or compensate their participants in crypto on a recurring basis. A Helium hotspot operator receives tokens via streaming for their network contribution — exactly the type of flow that Superfluid or Llamapay handle natively. On the customer side, a subscription to decentralized bandwidth or distributed storage (Filecoin, Arweave) can technically be structured as an automatic stablecoin payment.
Stripe and CeFi-DeFi bridges. Stripe launched native support for USDC payments on Base in 2024, enabling any merchant using Stripe Billing to offer crypto payment to their customers, with settlement in fiat. This integration — potentially the most impactful in the medium term — uses Stripe's existing rails (including automatic retry, failure management, and tax reporting) while accepting stablecoins. Gnosis Pay explores a similar approach on the debit side, with a Visa card funded by an on-chain wallet.
How to Set Up Recurring Crypto Payments for Your Business
Setting up recurring crypto payments depends on your desired level of decentralization and your team's technical capabilities.
1. Choose Your Billing Model
Three main options: periodic billing (one transaction per month, like a standard invoice), continuous streaming (Superfluid flow, billed by the second), or subscription NFT (membership token with an expiration date). Periodic billing works for SaaS with fixed plans. Streaming suits usage-based billing. NFTs work for community access and exclusive content.
2. Select the Chain and Stablecoin
To minimize gas fees and maximize adoption, Base, Polygon, and Arbitrum are the strongest choices in 2026. USDC is the recommended stablecoin for merchants targeting a global customer base, thanks to its regulatory positioning and liquidity. For merchants specifically targeting European customers, EUR-pegged stablecoins like Circle's EURC or Stasis's EURS are worth considering.
3. Integrate the Technical Solution
- Centralized option: Create a NOWPayments or CoinGate account, generate an API key, and integrate the subscription widget via the WordPress/WooCommerce plugin or directly through the REST API. Deployment time: a few hours.
- Semi-decentralized option: Use the Superfluid API to create payment streams, with a custom merchant dashboard. Requires a developer familiar with Solidity and ethers.js. Deployment time: 1–2 weeks.
- Stripe option: If the business already uses Stripe Billing, enable USDC payments on Base via the Stripe dashboard. The customer pays in crypto, the merchant receives fiat. Deployment time: minutes.
4. Manage Failures and Churn
Set up low balance alerts to warn the customer before a billing cycle. With Superfluid, monitor the liquidation buffer and notify the customer when their balance approaches the critical threshold. With centralized solutions, enable the automatic dunning emails provided by the gateway.
5. Ensure Tax and Regulatory Compliance
In the US, crypto received as payment is taxable income. Each USDC payment received must be recorded at its fair market value in USD on the date of receipt for tax purposes. Merchants should report crypto income on their standard business tax returns, and may need to issue 1099 forms to certain payees. Tools like Request Network facilitate traceability by generating on-chain invoices with automatic conversion. For individual crypto income, IRS Form 8949 is used to report capital gains and losses. Consult a tax professional to ensure compliance with federal, state, and any applicable international reporting requirements. If your business acts as an intermediary in crypto payments, evaluate whether FinCEN MSB registration or state money transmitter licensing is required.
FAQ
Can you set up automatic recurring payments in crypto like you can with a credit card?
Not in exactly the same way. On a blockchain, the native pull mechanism (where the merchant debits the customer's account) doesn't exist. The customer has to grant a token approval to a smart contract, which can then pull ERC-20 tokens within the authorized limit. Protocols like Superfluid work around this by creating a continuous payment stream rather than a periodic charge. The functional result is similar, but the underlying technical architecture is fundamentally different.
Which protocols let you pay a SaaS subscription in USDC or USDT automatically?
Superfluid is the most mature option for continuous USDC streaming on Polygon, Arbitrum, and Base. Sablier and Llamapay offer programmable payments with more flexibility on distribution curves. On the centralized side, NOWPayments provides a recurring subscription API supporting USDC and USDT, with optional automatic conversion. Stripe now accepts USDC payments on Base through its standard Billing module.
Is Superfluid reliable for receiving recurring payments from customers?
Superfluid has processed over $650 million in cumulative flows with no major security incidents reported on its audited smart contracts. On the technical reliability side, the protocol performs well on supported L2 networks. On the regulatory side, the picture is less clear: as a decentralized protocol, Superfluid doesn't hold any specific financial licenses in the US (such as MSB registration) or CASP authorization under MiCA in the EU. A merchant using Superfluid should assess their own regulatory responsibility, ideally with specialized legal counsel.
What happens if a customer's wallet doesn't have enough funds for a recurring crypto payment?
With a standard subscription smart contract (token approval + transferFrom), the transaction simply fails and the merchant doesn't get paid — with no native automatic retry mechanism. With Superfluid, the stream continues as long as funds remain, then stops when the balance hits the buffer threshold; a liquidation mechanism then recovers the security deposit to cover the final segment. In both cases, the merchant needs a notification system in place to alert the customer and prevent involuntary churn.
Are recurring crypto payments compliant with US regulations in 2026?
The regulatory landscape in the US is still evolving. A merchant using a licensed centralized gateway (Coinbase Commerce, NOWPayments) for crypto subscriptions is generally operating within established compliance frameworks — these providers handle MSB registration, KYC/AML, and reporting obligations. A merchant interacting directly with a DeFi protocol like Superfluid operates in a regulatory gray area. The SEC, CFTC, and FinCEN have not issued definitive guidance on fully decentralized protocols, and the distinction between true decentralization and a centralized service with a decentralized front end remains a point of active regulatory discussion. Clearer guidance is expected through 2026 and 2027.