Recurring crypto payments stopped being a thought experiment. Stripe now documents stablecoin subscriptions inside Stripe Billing, Solana-native processors run recurring programs onchain, and approval-based stacks debit self-custody wallets on a schedule. The plumbing has caught up. What still varies wildly: fees, chains, stablecoin coverage, and whether the provider expects you to manage wallets yourself.
​

This guide compares 10 platforms that actually offer recurring USDC, USDT, or PYUSD billing in production. We focus on integration complexity, supported stablecoins, fee structure, and target customer (SaaS, content creators, B2B invoicing). Fees below are shown only where the provider publishes a rate on a live page. Several providers in this market quote privately, and two have since been acquired, so confirm any number with the provider before you budget against it.
​

ERC-20 tokens have no native "pull" semantics. A merchant cannot debit a customer's wallet on a schedule the way a card network debits a bank account. Every recurring crypto payments stack has to solve this with either token approvals plus a relayer, a smart-contract subscription module, account abstraction (ERC-4337) with session keys, or the newer EIP-7702 delegation pattern that gives EOAs temporary smart-account powers.
​

That architectural fork drives every other tradeoff. Approval-based providers (Loop, Sphere) are cheap but require customers to trust a contract with a spending allowance. AA-based providers (Mesh, Privy) cost more in gas but give finer-grained control. Custodial providers (Bitwave, Helio) hide the complexity entirely but charge SaaS-style platform fees on top of network costs.
​

The matrix below uses each provider's public pricing and docs where a live page states a rate. Where it does not, the cell says so rather than carrying a number we cannot source. Fees are merchant-side unless noted. Integration complexity is rated 1 (drop-in widget) to 5 (raw smart-contract wiring).

Loop Crypto built one of the most widely deployed recurring crypto payments stacks. It uses a token-approval model: customers grant Loop's contract a spending allowance, and Loop debits on the merchant's schedule. In December 2025 the Loop team joined Lead Bank, and loopcrypto.xyz no longer resolves, so there is no live page publishing Loop's fee schedule or processed volume. Anything you read about either number, here or elsewhere, needs confirming with Lead directly.
​

Chains historically included Ethereum, Base, Polygon, Arbitrum, Optimism, and BNB Chain. Stablecoins: USDC, USDT, DAI, PYUSD. Integration is hosted-checkout-plus-API, so engineering time is typically under a sprint. Best fit: B2B SaaS selling to crypto-native customers who already hold stablecoins in self-custody wallets.
​

Sphere Pay runs subscriptions from its dashboard and API using a Solana-native program rather than token approvals. Sphere does not publish a rate card, so pricing comes from a sales conversation. Integration is a TypeScript SDK with React hooks.
​

Helio targets the creator economy. MoonPay announced its acquisition of Helio on January 13, 2025, and hel.io now redirects to MoonPay Commerce, which publishes no merchant rate card. Pay links there cover subscriptions, content, and products, with settlement in crypto, stablecoins, or fiat. Best fit: Discord communities, NFT memberships, and content creators monetizing subscriptions without an engineering team.
​

Bitwave is the closest thing to a stablecoin-native NetSuite. It handles recurring invoicing, automated reconciliation, and crypto AR/AP for enterprises using NetSuite, QuickBooks, or Xero. Pricing is custom enterprise SaaS and is not published. Bitwave supports USDC, USDT, PYUSD, and USDP across Ethereum, Base, Polygon, Arbitrum, and Avalanche.
​

Slash takes a different angle. It pairs a corporate card with stablecoin-funded recurring vendor payments, so businesses can pay SaaS vendors that bill in USD without manual treasury work. Slash does not publish a rate for the stablecoin leg. Best fit: crypto-native businesses paying traditional SaaS vendors on a schedule.
​

If you control both sides of the relationship (in-app subscriptions for a wallet, protocol, or game), AA-based subscriptions are increasingly attractive. ERC-4337 session keys let a customer authorize a contract to spend up to $X of USDC per month, with hard-coded constraints (max amount, time window, allowed contracts). Privy ships session-key tooling that pairs with any custom subscription contract; you bring the contract logic, Privy handles wallet UX, MFA, and recovery.
​

EIP-7702, live on Ethereum mainnet since the Pectra upgrade in May 2025, gives this power to existing EOAs without forcing wallet migration. A customer signs one delegation transaction, and their EOA can then execute scheduled pulls under contract-enforced rules. See EIP-7702 and stablecoins for the mechanics. Tradeoff: you are operating raw smart-contract infrastructure, which means audits, monitoring, and 24/7 ops.
​

Stripe Billing supports stablecoin subscriptions. If your business already uses Stripe Billing, enabling them is a dashboard setting plus a webhook update. Stripe's pricing page lists stablecoin payments at 1.5% of the transaction amount, inclusive of conversion to fiat, wallet and AML screening, fraud prevention, and gas sponsorship. That is the highest posted rate here, but it is the only posted rate here, and it buys one billing stack across cards and crypto. Stripe's docs list USDC on Tempo, Ethereum, Solana, Polygon, and Base, plus USDP and USDG on a narrower set.
​

Circle's stack is more à la carte. You compose Programmable Wallets (custodial or developer-controlled), the Smart Contract Platform for deploying a subscription contract, and Circle Mint for treasury. Fees scale with MAU and gas station usage. USDC and EURC only. For teams committed to USDC-only on regulated rails, this is the most flexible path; for teams that want multi-stablecoin, look elsewhere. Compare against accepting USDC payments for the non-recurring baseline.
​

Three questions decide most of it. First, what stablecoins do your customers actually hold? Solana-heavy audiences push you to Sphere or Helio; USDC-only fintechs gravitate to Stripe or Circle; multi-stablecoin B2B lands on Loop or Bitwave. Second, who owns the customer's wallet? Custodial flows (Helio, Stripe, Circle Programmable Wallets) hide complexity but constrain power-users; self-custody flows (Loop, Sphere, Privy, raw 7702) preserve user sovereignty but require wallet UX investment. Third, what is your engineering budget? Drop-in widgets ship in days; AA and 7702 stacks need weeks of contract work plus an audit.
​

The only merchant rate in this guide that comes from a live vendor page is Stripe's, published at stripe.com/pricing, with recurring support documented at docs.stripe.com. Two providers here have changed hands: Loop Crypto joined Lead Bank in December 2025 and its site no longer resolves, and Helio was acquired by MoonPay in January 2025 and now trades as MoonPay Commerce. The rest quote privately. Chain and stablecoin coverage is from each provider's developer documentation.
​