Name: Nozle
Brand: Nozle

Paid is one thing. Permitted is another.

One balance, debited on the event. One real-time gate — so 'paid' becomes 'permitted' before the next request lands.

Start free

See a wallet in flight

Five moves a wallet has to make. Ours runs them on one balance.

From the gate in your backend to a restore after payment — every step reads and writes one balance.

Cyclegate → debit → top-up → revoke → restore

01
Gate in one call
One call: can this customer do this thing? Plan, balance, and overage rules return a single yes/no with a reason.
02
Debit on the event
Each metered event drains the wallet as it lands. Balances reflect reality, not last night's batch.
03
Top up automatically
Auto-reload, granted credits, plan refresh — all add to the same balance with full provenance.
04
Revoke on plan change
Downgrades, cancellations and trial expiry change the subscription — and the gate follows it on the next check.
05
Restore on payment
Top-up paid, credits land — access returns on the next check. Same balance, same history, no resets.

A nightly cron isn't a wallet. A balance is.

When entitlements lag, customers get cut off mid-call or run free for hours. Both cost you trust.

Nightly entitlementsruns at 2am · reads yesterday

2:14pm

over cap

2:14pm

served

2am

cron

DAY → +12h

12h free traffic · refunds Monday · CS ticket

LATE

What you can't tell

who's over, who paid, who's still spending.

TICKET-?

Live walletreads on the event · writes on the event

2:14pm

at cap

2:14pm

gated

2:15pm

topped up

ACME · WALLET

balance 0 → $200 top-up → access restored

What you ship

who's over, who paid, who's mid-flight.

WALLET-7741

Four parts. One balance read by every surface that matters.

The gate that answers in one call, the wallet ledger that holds every debit and credit, the dunning that chases failed payments, and the surfaces that show the same balance.