The expensive failure in a usage-based business is often not the mispriced unit. It is the invoice that was calculated correctly, agreed by the customer, and then declined by the card that had cleared the base subscription every month without trouble. That card was approved once at a small recurring amount, and nobody re-checked what it could carry when a heavy month pushed the invoice several times higher.

Usage based billing moves that risk into every cycle, and EukaPay is the second payment path for the invoice that fails. Your own billing system counts the usage and sets the amount. EukaPay then collects it as an invoice or payment link payable in stablecoins or crypto, with fiat settled to your own bank account. This guide covers what changes on the payment side, why a large invoice can fail, and what a retry cannot fix.

Usage based billing charges a customer for what they consume in a period: API calls, compute minutes, active seats, messages sent, or data processed. Your own billing system counts those events, prices them, and writes the invoice. The output is an amount that can be different every cycle.

A flat subscription fee is one number, repeated. The card behind it was approved once at that number, and it keeps clearing at that number. Usage based billing takes that consistency away. The amount is a variable now, so the payment method has to carry the largest amount the model can reach, not the average one.

Metering happens where the events happen, which is inside your product. The counter, the rules that turn events into an amount, and the thresholds all live in your billing stack, next to the rest of your

SaaS billing management

.

That split matters when a payment fails. Metering answers how much the customer owes. Collection answers whether the money arrived. Two different systems answer those two questions, and a team that only instruments the first one may not know which of the two broke.

The schedule usually stays ordinary. Many usage models still invoice monthly, so the cadence looks the same as it does on

SaaS recurring billing

at a fixed amount.

Because the amount moves, a payment failure on a usage charge often gets triaged as a billing bug first. Someone checks the meter, confirms the number, and closes the ticket. The number was never the problem, so the invoice sits unpaid for another week while the real cause goes unexamined.

A card carries limits set by its issuer, and a business card can carry a per-item ceiling set by the customer's own finance team as well. An invoice several times larger than the usual one may cross either. The result reads as a decline, though nothing about the card is broken. It cleared last month, and it will clear next month at the usual amount.

There can also be an approval step that has nothing to do with the card network. Above a threshold, many finance teams route a payment through their own accounts payable process. A card that quietly auto-pays a small recurring amount may not be the instrument they intend to use for a large one, so a heavy usage month can stall even where the limit would have allowed it.

For that invoice, a second payment path is more useful than a third attempt on the same card. A EukaPay invoice or payment link carries the amount your billing system calculated, and the customer can pay it in stablecoins or crypto without that amount having to pass a card limit at all.

Your billing platform owns the retry schedule and the dunning sequence, and it should keep owning them. Both rest on an assumption that the payment is fundamentally good and only the timing was wrong: a balance that will be topped up, a card that will be updated before the next attempt. On a flat subscription, that assumption often holds.

It holds less often on a usage charge that exceeded a limit. Retrying the same instrument for the same amount can return the same answer on every attempt, and each attempt spends collection days you do not get back. Changing the instrument for that one invoice is more likely to work than changing the interval.

EukaPay does not run retries, dunning, or proration, and it does not manage plans or entitlements. Those stay in your billing system, alongside the rest of your

SaaS payments stack

. EukaPay covers the collection step: an invoice or payment link for an amount your system already set, payable in stablecoins or crypto, with fiat settlement to your bank account.

EukaPay is the path built for the invoice that does not look like the usual one. The amount travels on the invoice, and the exchange rate is locked on every conversion by default. A card on file suits the base subscription, and it keeps clearing at that amount. A manual bank transfer can work for the rare, large invoice a finance team already tracks by hand. Neither of those gives your customer a second way to settle a large usage amount, and EukaPay does.

EukaPay is one account for the collection and the fiat settlement behind it. It gives you instant crypto-to-fiat conversion at a locked exchange rate to remove your exposure to crypto price swings, support for most major cryptocurrencies like BTC, ETH, LTC, SOL, USDC, USDT, and settlement in USD, EUR, GBP, and CAD to your bank account. EukaPay locks the exchange rate on every conversion by default, on pay-ins and on payouts. A crypto payment confirms on-chain, so protection against chargebacks is a property of the payment method.

If your invoice amounts move with consumption, run EukaPay alongside the card flow you already have, and send the large or unusual invoice through it. Your billing system keeps counting the units and setting the amount. The invoice a card cannot carry gets a path that does not depend on a limit.

Sign up for a EukaPay account

to send your first usage invoice or payment link, or read the

API documentation

to see how invoices, subscriptions, and customers fit into a billing stack you already run.

What is usage based billing?

Usage based billing charges a customer according to how much of a product they consume in a period, such as API calls, compute minutes, or active seats, instead of a fixed recurring fee.

Why does a usage charge fail when the base subscription always clears?

The base subscription is the same number every cycle, so the card was approved at that number. A usage charge can arrive several times larger and meet an issuer limit or a company spending ceiling that the smaller amount never touched.

Can EukaPay meter my usage or work out the amount?

No. Counting the units and working out the amount happen in your own billing system. EukaPay collects the invoice or payment link once your system has set that amount.

Does EukaPay handle retries or a dunning sequence?

No. Retry logic and dunning stay with your billing platform. EukaPay can give the customer a different way to pay the specific invoice that failed, which is often more useful on a large invoice than another attempt on the same card.

Which cryptocurrencies can a customer use to pay a usage invoice?

Most major cryptocurrencies, including BTC, ETH, LTC, SOL, USDC, and USDT.

What currencies can a usage invoice settle in?

USD, EUR, GBP, or CAD, paid to your own bank account.

Do I need to write code to send one large usage invoice?

No. A single invoice or payment link can be created in the EukaPay dashboard. The API is there when you want your billing system to create them for you.

Can EukaPay send a usage invoice on a recurring schedule?

EukaPay subscriptions send invoices on a recurring schedule, at intervals from daily to annually. The amount on each invoice is set by your billing system, since EukaPay does not calculate usage.