florentin
Start free
ProductBillingCredits & balancesMeteringCheckoutCustomer portalAuth & accountsAPI keys & accessTeams & rolesFeature flagsWebhooks & eventsAnalyticsAI-first / MCPStripe integrationMulti-tenant & white-labelTax & currenciesSecurity & fraudImport & migration
SolutionsAI builders & APIsSaaSTools & automationsAgenciesStartupsEnterpriseMonetize an APIUsage-based billingPrepaid creditsSubscriptions & plansOutsource the portalLaunch a partner program
DevelopersQuickstartProvider docsCustomer docsAPI reference (Scalar)Webhooks & eventsAuth, errors, idempotencyMCP / AI agentStatusChangelog
Pricing
Start freeSign in
Home · Use Cases · Use case
Use case

Usage-based billing — pay for what's used.

Record usage per customer and settle it against balance or billing — in real time. Also as a hybrid of base fee plus usage.

Start free →See modules

Flat rates don't fit every product. But billing by actual usage takes more than a counter: usage must be captured without loss, aggregated per customer and settled correctly against balance or billing — and traceable for both you and the customer.

Florentin does this server-side: you record usage as amount + reason, Florentin settles it in real time against balance or plan and serves the breakdown via /usage/summary. Hybrid models of a fixed base fee plus a usage-based share are possible; request_id prevents double-counting.

Sound familiar

You don't want to build this yourself.

Flat rates don't fit everything. With usage-based billing you only pay for actual usage — Florentin records and settles it reliably.

  • Capture usage without loss and idempotently
  • Combine base fee and usage into a hybrid
  • Provide a breakdown per customer and period
How Florentin helps

Usage-based billing

✓
Real timeBalance drops instantly, usage visible immediately.
✓
Hybrid modelsFixed base fee plus a usage-based share.
✓
Read-outGET /usage/summary per customer and period.
✓
Reliablerequest_id prevents double-counting.
Matching modules

What's inside

01MeteringCount what counts — and bill it.→02Credits & balancesPrepaid balances that draw down as they're used.→03BillingEvery billing model — handled cleanly.→04Analytics & reportingSee what your business is doing.→05Stripe integrationFully integrated. Synced both ways.→
How it works

In three steps

Define a unit

Decide amount and reason per usage.

Record

Per usage via the credits API.

Settle

Against balance or plan, invoice via Stripe.

Build it yourself?

What Florentin saves you

Without Florentin

  • ✗ Build your own counters and aggregation
  • ✗ Model a fixed-plus-usage hybrid by hand
  • ✗ Build usage reports manually
  • ✗ Retries lead to double-counting

With Florentin

  • + Recording and aggregation server-side
  • + Hybrid plans out of the box
  • + Breakdown via /usage/summary and analytics
  • + request_id ensures clean counting
FAQ

Frequently asked

Base fee plus usage?
Yes — hybrid plans combine a fixed base fee with a usage-based share.
How do I see usage?
Via GET /usage/summary per customer and period, and in the analytics area.
In which unit is usage counted?
Freely: reason names the unit (calls, tokens, seconds, custom metrics), amount the quantity.
What happens on a failed attempt?
Via the request_id, retries are detected; no double recording occurs.
Related

Read on

01Monetize an API→02Prepaid credits→03Metering→

Build your product. We'll handle the rest.

Accounts, billing, credits, portal, access — integrated. Stripe fully included.

Start free →