Crypto Payments for SaaS

Renewals lost to declined cards

Involuntary churn is the quiet leak. A customer who loves the product gets a new card number, the renewal fails, the dunning emails go to spam, and the account lapses without anyone deciding to cancel. Cross-border customers have it worse, since issuers decline foreign SaaS charges at rates that would embarrass any other industry. Annual plans carry a different problem: a chargeback filed late in the term reverses the full invoice while the customer keeps eleven months of usage. Your processor treats each of these as your problem, prices your account accordingly, and adds a rolling review if your customer base skews toward countries its risk model dislikes.

Finality on a year of service

A crypto payment for an annual plan confirms on-chain and cannot be reversed by an issuer six months later. The invoice you collected stays collected for the whole term you granted. Settlement is non-custodial, landing in a wallet your company controls the moment it confirms, so revenue recognition and cash arrival stop being two different events. Cross-border stops being a category at all. A customer in any country pays the same way from the same kind of wallet, with no issuing bank in the path to decline the charge. For a business selling to developers, the buyers are unusually likely to hold stablecoins already.

Adding crypto to your billing page

Most SaaS teams start by offering crypto on annual and lifetime plans, where finality matters most and per-invoice friction matters least. The API creates a payment when an invoice is due, the customer gets a hosted checkout, and a webhook fires on confirmation so your entitlement system extends access with no manual step. Developer-heavy customer bases lean hard on stablecoins, and on eligible routes the gasless checkout lets a customer pay USDC without holding the chain's gas token, which removes the classic first-purchase failure. Monthly plans work as emailed payment requests. Nothing about your card billing has to change, since crypto runs beside it as an option.

The terms, the same for every vertical

The fee is 0.5% per confirmed payment, prepaid. New accounts start with $50 of live credit, roughly the first $10,000 processed. Coverage spans 14 mainnet chains, listed live in the accepted coins directory. Checkout ships hosted, through the WooCommerce and OpenCart plugins, or by API, and settlement is non-custodial on every route. Legal obligations that apply to your business remain yours, and our acceptable-use policy applies to every account.

Common questions

Can I offer crypto only on annual plans?

Yes. Each payment is created individually through the API or dashboard, so you decide which plans surface the option. Most teams start with annual and lifetime tiers, where a single confirmed payment covers a long entitlement and the absence of a late chargeback protects the most revenue.

How does my app know when to extend a subscription?

A webhook fires when the payment reaches on-chain confirmation, carrying the payment id you attached at creation. Your billing system treats it like a successful card capture: extend the term, issue the receipt, done. Because confirmation is final, there is no later event that takes the renewal back.

What will developer customers actually pay with?

Mostly stablecoins, which they already hold for infrastructure spend and payouts. On eligible routes the checkout is gasless, so a customer with only USDC in a wallet can complete payment without buying a gas token first. Volatile coins are available too for the customers who prefer them.