Version 26.2.4 is now live for all clients. It goes after costs that never show up on an invoice. A payout fails because a wallet quietly runs dry. A user opens a ticket because they can't tell whether their deposit arrived. Finance spends an afternoon mapping transfers to legal entities by hand. All three, targeted.
Low-balance notifications: catch the shortfall before your users do
Every wallet now has its own balance threshold, set in the wallet's currency. When the available balance falls below it, you get notified automatically, with enough lead time to top up before an end-user withdrawal fails.
Failed withdrawals are the most expensive kind of failure a payment operation has: the user has already done everything right, and the platform still says no. The threshold turns that scenario from an incident into a routine top-up.
There is a reason this feature leads the release. An end user never reads a failed withdrawal as an operations slip. They see a platform that didn't pay, and they tell others. We understand what that moment does to our clients' reputation, so we build controls that preempt it: preventing it costs one threshold setting, while rebuilding trust costs bonuses, support hours, and win-back campaigns. We think of it simply. Our clients' user retention is our retention.
How to enable: open any wallet, set the threshold value, done. Each wallet is configured independently.
Callbacks before confirmation: your users see their payment immediately
The system now fires a callback the moment an incoming transaction is detected on-chain, before it collects the confirmations required for Confirmed status. Use it to show the payer that their payment has been seen and is simply awaiting network confirmations.
The minutes between "sent" and "confirmed" are where deposit anxiety lives and support queues grow. An immediate "payment detected" message takes those minutes off your support team's plate.
Wrong-network deposits: one click back to the source
When a deposit sent on the wrong network is automatically re-created on the correct one, the Duplicated Blockchain deposit event now links directly to the original deposit. Instead of tracing callback and tracking IDs manually, open the event and follow the Initial deposit reference. Deposit details also gain copy buttons for the Tracking ID and Callback URL.
For white-label operators: see everything, change nothing
This block is for our white-label clients, the businesses running their own branded payment platform on B2BINPAY infrastructure.
- Read-only Admin UI pages for Orders, Payouts, Blockchain Wallets, Global Wallets Balance History, and Global Wallets Staking: full operational visibility with zero risk of accidental edits.
- Audit-log filtering by event type. Isolate a single event class, for example Payouts blocked or Password changed, across brand, group, user, and legal-entity logs.
- Owner ID and Legal Entity Name columns in exported Transfers and Wallets reports, so reconciliation across entities no longer needs manual mapping.
- USD-normalized transfer volumes in Dealing, matching what swaps already show and removing manual rate calculations.
One more thing about the Admin UI, and it is deliberate. We keep adapting the new admin interface to the existing Client UI: the same design system, the same patterns and controls. Anyone on your team who has worked in the client B2BINPAY interface can navigate the admin side without retraining.
Workflow improvements
Multi-select currency filters across Wallets, Deposits, Payouts, Transfers and more, with paged loading that removes the freeze on long currency lists. An Operation ID filter on the Callbacks list for faster investigations, including callbacks with no associated transfer. Operation-log comments now display in your selected language. Plus a set of resolved issues, including a false insufficient-fee error on certain token withdrawals such as USDT-TRX and USDT-BSC.
Version 26.2.4 is available now.
Log in to configure your balance thresholds, or see the full release notes in the documentation.
.svg)
