BINK Business

Nine products.
One set of books.

Most business finance stacks are a collection of tools that agree with each other on a good day. BINK Business is one ledger, one permission model, one approval engine and one audit log — and the products are the surfaces onto them.

Three domains
TreasuryWhere the money sits, and what it is doing.Treasury ManagementLiquidity ManagementMulti-Entity Accounts
OperationsHow money leaves, and who may move it.Team WalletsCorporate CardsGlobal PayoutsBill Pay & AP
Intelligence & ControlWhat happened, and what still needs a decision.Financial AnalyticsAudit & ReconciliationApproval Workflows
LedgerOne, double-entry
PermissionsOne model, thirty-two scopes
ApprovalOne four-eyes engine
AuditOne log, that you own
Underneath all of it

Four things, shared.

This is the difference between a platform and a bundle. Each of these exists once, and every product on this page is a view onto it rather than its own copy.

SharedWhat it isWhat that means in practice
The ledgerEvery balance is a position in one double-entry ledgerTreasury, cards, payouts and analytics all read the same figures
The permissionsOne set of named scopes across the whole platformA role granted for payouts does not silently grant settlement
The approvalsOne engine, refusing self-approval everywhereA decision is governed the same way wherever it is raised
The audit logOne immutable record, readable and exportableWho did what, with before and after, without asking BINK
Why it holds

Control, not coverage.

BINK’s strength is not how many places it reaches — it is what it refuses to let happen on the way, and what it can prove afterwards.

One set of numbers

Balances, treasury positions, card spend and reporting are all projections of the same ledger. There is no second system to reconcile against, because there is no second system.

One access model

Thirty-two named permissions across seven roles you can extend, tuned per person. Access to a new product is a permission, not another account and another password.

One approval engine

The same four-eyes mechanism governs every decision that needs a second person — refusing self-approval and reporting the attempt as a critical incident.

One audit trail

Policy changes, role changes, approvals and money movements write to a company log with actor, role and address — immutable, and exportable by the business itself.

Retries that stay safe

Money-moving requests carry idempotency keys and run under serializable isolation, so a network retry or a concurrent request cannot become a second payment.

Gates before, not after

Verification state, sanctions and fraud evaluation are completed before a request is accepted rather than reconciled afterwards.

The platform

Three domains, nine products.

Treasury is where money sits. Operations is how it leaves and who may move it. Intelligence and control is what happened, and what still needs a decision.

Scope, stated

What this is today.

Every product page carries its own boundary. These are the two that apply across the whole platform.

A BINK login owns one registered business, and money moves between accounts on BINK rather than out to external banks. Both limits are stated on the pages they affect rather than left to be discovered.

Who this is for
Businesses where more than one person touches money, and where somebody will eventually have to explain a decision that was made months ago.
What holds it together
Not a bundle of products with one login — a single ledger, permission model, approval engine and audit log that every surface is built on.
One business per login
A BINK login owns one registered business. Group structures, parent and subsidiary entities and entity switching are not available today.
Where money can go
Money moves between accounts on BINK. Outbound bank rails are not connected, so payouts are a request-and-approval architecture rather than a disbursement service today.
What is measured
BINK publishes no volume, uptime, latency or customer figures on these pages. Where a number would be a measurement nothing takes, the capability is described instead.
BINK Business

One ledger. One record.

Treasury, operations and control that agree with each other because they are reading the same books.