Home / Blog / Solutions

Usage based subscription billing in crypto: choosing the plan structure

Compare four ways to price usage in a crypto subscription: flat plan, base fee with overage, prepaid credits and pay as you go, with USDC examples.

Dmitry Rusanov Dmitry Rusanov Sep 20, 2026 Updated Oct 26, 2026 10 min read
crypto-subscriptions lifestyle editorial photography

Quick answer

Usage based subscription billing in crypto comes down to one choice: how much of the price is fixed and how much follows consumption. There are four workable plan structures: a flat subscription, a base fee with included usage and overage, prepaid credit packs, and pay as you go invoicing. Pick the one that matches how much your customers’ usage varies, who approves their spend, and how much unpaid usage you can afford to deliver. Price in US dollars, settle in stablecoins, and bill the fixed part and the variable part as separate payments.

Who this guide is for

This guide is for founders and product owners who sell an API, an AI product, hosting or another SaaS with variable consumption and want to charge for it in crypto. It covers the commercial decision: what the plan looks like, how the numbers are set, and what the customer sees when paying from a wallet.

The engineering side is a separate job. Counting events, rating them and reconciling stablecoin receipts against invoices is covered in the guide to usage based crypto billing, which walks through the meter-to-settlement loop step by step. Read this page first if the pricing model is still open; read that one when the model is decided and the team is ready to build.

The distinction matters because the most common failure is not technical. Teams build an accurate meter and then attach it to a plan that customers do not understand, that never triggers overage, or that leaves the business carrying a month of unpaid usage from accounts it barely knows.

a bunch of bitcoins sitting on top of each other

Four plan structures for usage based subscription billing

Each structure trades bill predictability for the customer against payment risk for you. A flat plan is the most predictable and ignores usage; pay as you go follows usage exactly and puts the whole period at risk until it is paid.

Plan structureWhat the customer paysPredictability for the customerUnpaid usage risk for youTypical fit
Flat subscriptionThe same amount every intervalHighestLow: one interval at mostUsage is similar across customers or cheap to serve
Base fee with included usage and overageA fixed renewal plus a separate overage payment after the period closesHigh for the base, variable for overageMedium: overage is delivered before it is paidAPIs and SaaS where most customers stay near a typical volume
Prepaid credit packsA one-time purchase of a block of units, repeated when the balance runs lowThe customer decides when to spendLowest: service stops when credits run outNew or anonymous accounts, AI inference, spiky workloads
Pay as you go invoiceLast period’s usage, requested after the period endsLowestHighest: the whole period is delivered before paymentKnown business accounts with procurement review
Plan structures compared by predictability and payment risk

Most products end up with two of these side by side. A common pairing is a base plan with overage for regular customers and credit packs for new sign-ups who have not yet earned payment terms. Another is a flat plan for small accounts and invoicing for the few large accounts whose usage cannot be predicted. If you are weighing meters against credits in general, not only for crypto, the comparison of metered billing software vs credit billing goes deeper into that trade-off.

How to choose: five questions about your customers

The right structure follows from customer behavior, not from what competitors publish. Answer these five questions with real usage data from your product before writing a pricing page.

  1. How much does usage vary between months for the same customer? If a typical account moves less than a third up or down, a flat plan or a generous base allowance works. If usage swings several times over, overage or credits are needed.
  2. How much does one unit cost you to serve? When the marginal cost is real, as with model inference, GPU time or bandwidth, a flat plan lets heavy users erode your margin. When it is close to zero, a flat plan is often simplest.
  3. Who approves the spend? An individual developer paying from a personal wallet prefers a known amount or a prepaid balance. A company with a finance team may prefer an invoice it can review before sending stablecoins.
  4. How fast can an account consume value? If a new account can run up a large bill in a day, through abuse or a runaway script, start it on prepaid credits and move it to a base plan once it has a payment history.
  5. Do your customers already hold stablecoins? Customers who keep USDC or USDT in a wallet handle recurring charges well. Customers who would have to buy crypto for every payment are better served by fewer, larger payments such as credit packs or annual plans.
Founder and finance lead choosing a billing model at a conference table

Setting the numbers: base fee, allowance and overage rate

Set the allowance so that a typical customer stays inside it, price overage above the per-unit price of the allowance, and keep units round enough that a customer can check the bill by hand.

  • Allowance. Start from the median monthly usage of your active accounts. An allowance far above it means overage never triggers and the plan is flat in practice; an allowance below it turns every invoice into a surprise.
  • Overage rate. Charge more per unit than the allowance effectively costs, so that moving to a larger plan is the cheaper option for customers who exceed it every month.
  • Units. Bill per 1,000 requests, per million tokens or per GB-month rather than per single event. Round units make statements readable and reduce disputes over rounding.
  • Currency. Price in US dollars and settle in a dollar stablecoin. Customers compare your price with card-billed competitors in dollars, and your books stay in one currency.

A hypothetical example shows how the pieces fit. An API plan costs 49 USD per month and includes 500,000 requests, which is about 0.098 USD per 1,000. Overage costs 0.12 USD per 1,000 requests. A credit pack of 1,000,000 requests costs 110 USD.

CustomerRequests in the monthBase plan with overageCredit packs only
A, steady380,00049 USD, no overageOne pack, 110 USD, with 620,000 requests left for later
B, growing740,00049 USD plus 240 × 0.12 = 28.80 USD overage, 77.80 USD in totalOne pack, 110 USD, with 260,000 requests left
C, new accountUnknownRisky: overage is delivered before paymentSafe: service stops at zero balance
Hypothetical bills under two plan structures

Customer B is the signal to watch. If an account pays overage three months in a row, offer a larger base plan before it starts to feel the overage as a penalty. Customer C is why credits exist: they let you serve an account you know nothing about without extending it credit.

What the customer sees when paying from a wallet

Explain the bill in two parts: a fixed renewal that repeats automatically, and a usage charge that arrives as a separate payment request with a statement. Customers accept variable bills when they can see the arithmetic before they pay.

Card billing hides the split: one card charge simply comes out higher in a busy month. With crypto the split is visible and that is an advantage if you design for it. The base fee renews for the same amount every interval, so the customer knows what leaves the wallet and when. The usage part is a one-time payment for a closed period, sent with a statement that lists the included allowance, the measured usage and the rate.

  • Show current usage and the projected overage inside your product before the period closes.
  • Send the overage request with the statement, not just an amount and an address.
  • Give a clear due date and say what happens to access if the usage charge is not paid.
  • Let customers cancel the base plan and buy credits instead, so that a quiet month does not cost them a full plan.
Two colleagues reviewing coloured cards on a wall display

How these plans map to Zyrox

Zyrox renews a fixed amount at a fixed interval and takes one-time payments of any amount. Your product keeps the meter and decides the usage amount; Zyrox collects each payment and sends funds straight to your wallet.

  • Flat plan or base fee. A subscription payment link sets the amount in USD and the interval: daily, weekly, monthly or yearly. The customer pays the first charge from a wallet, and later charges are created automatically on the same network and token. A failed charge is retried up to five times, after which the subscription is paused.
  • Overage and pay as you go. Bill the closed period as a one-time payment: a payment link with the computed amount, or a checkout session in payment mode through the Stripe-compatible API.
  • Credit packs. Sell each pack as a one-time payment and add the credits to the account when the payment webhook arrives.
  • Tracking. Webhooks report the first payment (checkout.session.completed) and each renewal (invoice.paid), and subscription links accept a package_id to tag which plan was bought.
  • Customer control. Customers see their subscriptions, billing history and next billing date on a Zyrox page linked to their wallet address, and can cancel there.

Payments can be made in USDC and USDT on Ethereum, Arbitrum, Base and Optimism, in USDT and TRX on Tron, and in BTC and ETH. Because the recurring amount is fixed, do not try to fold usage into the renewal by changing it every month; keep the base and the usage charge apart, as in the plans above.

Common pricing mistakes

  • An allowance nobody reaches. The plan is flat in practice and heavy users are subsidized by light ones.
  • Overage below cost. Growth in usage reduces margin instead of increasing it.
  • Prices in a volatile token. The same plan costs a different amount every week and finance cannot forecast revenue.
  • Overage without warning. The first sign of overage is the payment request, which turns a pricing feature into a support ticket.
  • Credit for unknown accounts. Pay as you go terms for accounts without history leave the business funding their usage.
  • No path between plans. Customers who keep paying overage, or keep buying credits, should be offered the plan that fits them.

None of these depend on the payment rail. They are pricing decisions, and they are cheaper to fix on a pricing page than after the first disputed bill. Renewal failures need their own policy as well; the guide to crypto subscription payment retries covers grace periods and reminders.

Woman using a laptop showing charts and a table

Launch the plan with direct wallet settlement

Once the plan structure and the numbers are set, collection is the easy part. Zyrox renews the fixed part of the plan automatically, takes the variable part as one-time payments, and sends every payment straight to your own wallet without holding the funds.

Zyrox is free until the end of 2026 and charges 0.5% of successful payments from 2027. Create an account, set up a test subscription and a test usage payment, and check that both reach your wallet before you publish the new pricing.

Frequently asked questions

What is usage based subscription billing?

It is a subscription where at least part of the price depends on what the customer consumes, such as requests, tokens, storage or compute time. The most common form is a fixed base fee that includes some usage, plus a charge for usage above it.

Is a base plan with overage better than pure pay as you go?

For most self-serve products, yes. The base fee gives the customer a predictable bill and gives you predictable revenue, while overage still captures heavy usage. Pure pay as you go suits business accounts that review each invoice before paying.

Can a crypto subscription charge a different amount each month?

With Zyrox the recurring charge is a fixed amount per interval. Bill the variable usage separately as a one-time payment for the closed period, through a payment link or the Stripe-compatible checkout API.

How should the overage rate be set?

Above the effective per-unit price of the included allowance and above your cost to serve. That way growing customers move to a larger plan instead of paying overage indefinitely, and extra usage adds margin.

When are prepaid credit packs the better choice?

For new or anonymous accounts, for workloads that can spike quickly, and for customers who prefer to pay occasionally rather than every month. Credits are paid before the service is used, so there is no unpaid usage to collect.

What happens if a subscription renewal fails?

Zyrox retries a failed charge up to five times and pauses the subscription after five consecutive failures. The merchant is notified by email, and so is the customer if they gave an email address; your product decides what happens to access in the meantime.

Should prices be set in USDC or in US dollars?

Set prices in US dollars and accept dollar stablecoins such as USDC or USDT. Customers compare prices in dollars, and Zyrox subscription amounts are set in USD.

Dmitry Rusanov
Written by

Dmitry Rusanov

Product designer at Scrile. Focused on user value and business outcomes. Writes about interface decisions, design-system economics, and where UX investment actually pays back.

Reviewed under our Editorial standards.

Accept crypto without giving up control

Subscriptions and one-time payments, settled to your own wallet. No custody, no frozen funds, no chargebacks.