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

Prepaid credits — sell balance.

Sell credit packs that get consumed as they're used — with expiry, auto-top-up and alerts. Ideal for variable usage and a low barrier to entry.

Start free →See modules

Not every customer wants to commit to a subscription — especially with irregular usage, prepaid credits are the more natural choice. They lower the barrier to entry and make costs predictable. The hard part is behind the scenes: balances must be booked atomically, expiry and roll-over need rules, and the customer should be warned in time before running dry.

Florentin manages all of it: credit packs with their own price and expiry, usage via the credits API, auto-top-up above a threshold and low-credit alerts by mail, webhook or Slack. Credits can be combined with subscriptions and run as a shared team pool.

Sound familiar

You don't want to build this yourself.

Not everyone wants a subscription. Prepaid credits lower the barrier and fit variable usage. Florentin manages balances, expiry and top-ups.

  • Book balance atomically and correctly
  • Rule expiry, roll-over and auto-top-up
  • Warn customers in time before running dry
How Florentin helps

Prepaid credits

✓
Bundle packsCredit bundles with their own price and expiry.
✓
Auto-top-upAuto-reload above a threshold.
✓
AlertsLow-credit alerts by mail, webhook or Slack.
✓
Team poolShared balance for a team, with transfer.
Matching modules

What's inside

01Credits & balancesPrepaid balances that draw down as they're used.→02MeteringCount what counts — and bill it.→03BillingEvery billing model — handled cleanly.→04Customer portalYour customers manage themselves.→
How it works

In three steps

Create packs

Define credit bundles with price and expiry.

Sell

Offer via checkout or in the customer portal.

Consume

Florentin draws down, alerts and auto-reloads.

Build it yourself?

What Florentin saves you

Without Florentin

  • ✗ Build credit logic yourself, error-prone
  • ✗ Scatter expiry and roll-over in code
  • ✗ Let customers hit 0 without warning
  • ✗ No way to model team balances

With Florentin

  • + Atomic recording of balance and usage
  • + Configurable: never, after X days or roll-over
  • + Auto-top-up and alerts before running dry
  • + Shared team pool out of the box
FAQ

Frequently asked

Do credits expire?
You decide: never, after X days, or with roll-over into the next month.
Can I combine a plan and credits?
Yes — a plan can grant monthly credits, and customers buy more on top.
How is usage recorded?
Via the credits API as amount + reason; the balance drops in real time, request_id prevents double-counting.
Is there shared balance for teams?
Yes — a team can use a shared credit pool, including transfers.
Related

Read on

01Usage-based billing→02From tool to business.→03Credits & balances→

Build your product. We'll handle the rest.

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

Start free →