Business · Liquidity

Not one number.
Four, that mean different things.

“How much is there” and “how much can I use” are different questions, and a single balance answers neither well. BINK keeps available, reserved, operational and contingency apart — with thresholds you set and a status derived from them rather than assessed by eye.

Talk to us See the architecture

Status, derived

HealthyAbove the alert threshold

LowBetween alert and minimum — raised, still working

CriticalBelow the minimum you set

Both levels are yours and are changed by an audited action. No balance or level is shown here — that is your information, not a sample.

PoolsOne per supported currency

BucketsFour, tracked separately

ThresholdsYours, and audited

HistoryAppend-only, never edited

Composition

What a pool is made of.

Four buckets, tracked apart rather than netted into a total. Netting them is how a treasury ends up spending money it had already promised to something else.

BucketWhat it isWhat moves it

AvailableFree to be drawn against right nowConversions, operator movements

ReservedCommitted against something already promisedReleased when the commitment clears

OperationalHeld back for day-to-day movementSet by policy, moved deliberately

ContingencyHeld back on purpose, not in circulationOnly an operator, with a reason

The loop

Set, watch, act.

The cycle a treasury operator actually runs — and the only part of it that requires a person is the last step.

SetYour thresholdsAlert and minimum levels, per pool, changed by an audited action.
WatchStatus derivedHealthy, low or critical — computed, never judged by eye.
AlertOn the breachA crossing raises an alert as part of the same flow.
ActAnd record itA movement or rebalance, written with its reason.

What you get

Positions that stay true.

Most of this exists so that the number you read is the number that was there when you read it.

Thresholds you own

Each pool carries its own alert and minimum levels rather than inheriting a platform default. Changing one is an audited action with an author, not a settings toggle nobody can trace.

Status is computed

Healthy, low and critical follow from comparing a pool against its own thresholds. Nobody decides a pool looks fine, and nobody has to be watching for the state to change.

Movements are atomic

A movement is applied as a database-level increment inside a transaction, so two movements arriving together cannot both act on the same starting balance.

A history that rebuilds

Every movement writes an event carrying the balance before and after. Because the log is only ever appended to, a pool’s position at any past moment can be reconstructed from it.

Rebalance with a check

Moving between pools verifies the source can actually cover the amount first, then updates both sides and writes both events — or does none of it.

Conversions keep it true

An executed conversion moves the affected pools and re-derives their status inside the same flow, so the position is never briefly wrong while something catches up.

Operational detail

How it behaves.

What is automatic, what is deliberate, and where the line between them sits.

These are BINK’s own operating pools. There are no external liquidity providers, correspondent banks, credit lines or automated market sweeps behind them, and none are claimed.

Scope: These are the platform’s operating pools — one record per supported currency. They are the position BINK draws on, not a customer account.
Starting state: A pool holds exactly what has been moved into it. There is no capacity figure, no facility and no headline number, and none is published.
Who can move it: Two sources: an executed conversion, which moves pools automatically, and an operator, whose movement is recorded with a reason and attributed to them.
Rebalancing: An operator action with a sufficiency check. BINK does not run scheduled sweeps between currencies and does not describe rebalancing as automatic.
Alert repeats: A persistent breach stays one alert inside its cooldown window rather than re-raising, so a real condition does not train a team to ignore notifications.
Currencies: Pools exist for the six ledger currencies. Which are relevant to a given business depends on what it actually holds.

In the platform