Two people, always
A payout cannot be approved by the account that requested it. Separation of duties is enforced in the code rather than described in a policy document nobody reads.
Business · PayoutsMoney out is the
Money out is the
decision that needs two.
Outbound payment is where a control failure is expensive and irreversible. BINK treats a payout as a request that must be gated, reserved against a real balance, approved by someone other than the person who asked, and recorded at every step.
What a payout record carries
ReferenceA unique identifier for the request
AmountIn minor units, with its currency
DestinationBank, InstaPay or wallet, as a kind
RequesterWho asked, recorded on the record
ReviewerWho decided, and when
RateThe FX snapshot taken at settlement
Requester and reviewer are separate fields because they must be separate people.
SeparationRequester is never the approver
IdempotentA retry cannot double-pay
BalanceChecked against the ledger
LifecycleSix states, fully audited
Who does what
Nobody moves money alone.
Each stage has an actor and a condition that must already be true before it can happen. The most important row is the second one.
StageWho actsWhat must already be true
RequestA member with the payout permissionKYB passed, fraud cleared, reserve adequate, not frozen
ReviewA different account, never the requesterThe request is pending and still valid
ProcessThe platform, once approvedThe approval is recorded and attributable
CompleteAn operator, on confirmationDisbursement confirmed outside the platform today
Fail or retryAn operator, with a reasonThe reason is written to the record
The lifecycle
Requested to resolved.
- RequestedAnd gatedKYB, fraud, freeze and reserve are checked before it is accepted.
- PendingAwaiting reviewHeld for a second person to decide.
- ProcessingApprovedMoved forward by someone other than the requester.
- SettledOr refusedCompleted, rejected or failed — each with its reason.
What you get
Controls that hold under load.
Most payout incidents are not exotic — they are a duplicate, a race, or one person acting alone. Each of those has a specific answer here.
Idempotent by key
A request carries an idempotency key unique to the business. Replaying it returns the original payout instead of creating a second one — a network retry cannot become a duplicate payment.
No double-spend window
The balance check and the reservation happen inside a serializable transaction with bounded retry, closing the gap where two concurrent requests could each see enough funds.
Gated before accepted
Verification state, sanctions and fraud evaluation are completed before a request is accepted — awaited, not fired off and hoped for.
Freeze the whole business
Payouts can be disabled for a business outright, and the check sits in the acceptance path — so a freeze stops new requests rather than queueing work that must later be unwound.
Every transition recorded
Requested, reviewed, processed, completed, rejected, failed — each with an actor, a timestamp and a reason, written to an audit trail.
Operational detail
How it behaves.
What the request and control architecture guarantees — and where execution currently hands over.
BINK’s payout capability today is the request, control and accounting architecture: gating, approval, reservation, lifecycle and audit. Outbound bank rails are not connected, so BINK claims no corridors, delivery times or country coverage, and the final disbursement step is confirmed outside the platform.
- Balance source
- Availability is computed from the double-entry ledger rather than a cached figure, so a payout is never accepted against a balance that had already been committed elsewhere.
- Reserve
- A rolling reserve is taken into account when deciding whether a request can be covered — the question is what is genuinely free, not what is nominally held.
- Rate snapshot
- Where a payout settles in a different currency, the rate used is captured on the record with its timestamp, so the conversion can be explained later.
- Rail eligibility
- Destination kinds are region-aware — a rail available in one market is not offered in another simply because the field exists.
- Batch
- Payouts are individual requests. Bulk or batch payout submission is not a capability BINK offers today.
- Delivery
- BINK publishes no delivery time, corridor list or country count, because no outbound rail is connected to measure one.
In the platform
Around a payout.
BINK Business
The whole platform.
Treasury
Where the money sits, and what it is doing.
Operations
How money leaves, and who may move it.
Intelligence & Control
What happened, and what still needs a decision.
Global Payouts
One request, two people.
Gated on the way in, reserved against a real balance, approved by someone else, and recorded at every transition.