← The platformWallets & invoicing

Money, handled.

Credit wallets with auto top-up, invoices that reconcile themselves, payments on the processor you choose, and usage forecasts your finance team can actually plan around.

Updated August 2026
Auto top-upsInvoicingTax & paymentsForecasting
Wallet · Pro plan12,400 credits
Auto top-up on
Burn-down · this cycle62% consumed
INV-2041 · July usageOpen
INV-1988 · June usagePaid
Why it matters

Close the books without a spreadsheet.

01Reconciles itself

Every invoice line traces to the usage event behind it. Finance drills from a total to raw usage in two clicks.

02Auto top-ups keep pipelines running

Balances that cross a threshold trigger a one-click link — or an opted-in auto-charge — before anything stops working.

03Processor-neutral

Stripe, Razorpay, Adyen or Braintree — switch or add a processor without re-platforming your billing.

How it works

Three steps. No engineering ticket.

1Map events to credits

Set the credit cost per event type in the dashboard — the same metering ledger drives the burn-down.

2Track burn-down live

Customers and your team see the same real-time balance, no separate systems to keep in sync.

3Top up or invoice

Cross a threshold and a top-up link fires automatically; period ends and an invoice assembles itself.

3credit types tracked in one wallet — paid, granted, trial
4payment processors supported, mix and match by region
hourlysync to your data warehouse for finance
Under the hood

A balance customers and finance both trust.

A wallet isn't a separate system bolted onto billing — it's driven by the same metering ledger that produces invoices. In the dashboard, you set a credit cost per event type (a token, an API call, a compute-second), and every event that lands in the ledger burns down the wallet by that amount in real time. There's no nightly reconciliation job trying to make two systems agree; the balance a customer sees and the balance that determines their invoice are computed from the same source.

Wallets hold more than one kind of balance at once. Paid credits, promotional grants and trial credits are tracked separately inside the same wallet, and grants burn down before paid credits — so a promo or trial allowance gets used first, and a customer's paid balance isn't quietly consumed by usage that was meant to be free. Grants can carry their own expiry window for trials or launch promos; paid credit balances don't expire on their own.

Top-ups are threshold-based: when a balance crosses a configured line, Kribana can fire a one-click payment link immediately, or — with explicit customer opt-in — charge automatically without anyone needing to click anything. That threshold check runs continuously against the live ledger, not a periodic batch job, which is what prevents the scenario every usage-based product fears: a customer's balance hitting zero mid-batch-job with nobody watching.

At invoice time, nothing needs to be re-derived. Every line on an invoice traces directly back to the raw usage events that produced it, so finance can drill from a total down to the individual events behind it in two clicks instead of chasing a spreadsheet. And because wallets sit above the payment processor layer, topping up or paying an invoice works the same way regardless of which processor — Stripe, Razorpay, Adyen or Braintree — is actually moving the money.

How this plays out in practice

Their wallet dropped to 3% mid-batch on a Saturday morning. It was topped up in six minutes. Nobody on either team was awake for it.

DI
A data infrastructure companyData infrastructure
Read the full case study →
0pipeline stoppages since launch
Illustrative scenario, not a verified customer metric — full context in the case study.

FAQ

Can I mix paid credits, promotional grants and trial credits in the same wallet?

Yes. A single wallet can hold paid credits, promotional grants and trial credits at the same time, tracked as separate balances internally even though the customer sees one number. Grants and trial credits burn down first, so a customer's paid balance is protected from being consumed by usage that was meant to be covered by a promo or trial allowance.

What happens if a wallet balance hits zero mid-request?

That's an entitlement check, not a billing surprise after the fact — Kribana can be configured to block further usage the moment a wallet empties, or to allow a grace amount while a top-up completes, depending on how strict you want enforcement to be. Because the threshold check runs against the live ledger continuously, a top-up link or auto-charge typically fires well before a balance actually reaches zero.

Do auto top-ups require the customer to opt in?

Yes — auto-charge top-ups only happen after a customer has explicitly opted in. Without that opt-in, crossing the threshold sends a one-click payment link instead, so nobody's card gets charged automatically without their prior agreement. Both modes use the same threshold configuration; only the follow-through action differs.

Do unused credits expire?

It depends on the type. Grants — the free credits issued for trials, launch promos or make-goods — can carry an expiry date you set when issuing them. Paid credit balances don't expire on their own; a customer's purchased credits remain in their wallet until they're used.

How does a wallet balance reconcile with the invoice at the end of a billing period?

There's no separate reconciliation step required, because there's nothing to reconcile — invoices are assembled directly from the same ledger that drives the wallet balance, so every line item traces back to the specific usage events behind it. Finance can drill from an invoice total down to raw usage in two clicks instead of cross-checking two systems that might disagree.

Send your first event today.