%20(1).avif)
B2BINPAY version 26.2.14 is live for all clients. This article covers four releases, 26.2.11 through 26.2.14, and this time we'll focus mostly about things that stop happening.
Deposits stop sitting in Created for half an hour after a brief infrastructure interruption. Transfers stop hanging in Unconfirmed when two currencies are returned from a blocked transfer at once. Payout approval notifications stop arriving for people who were never on the approvers list. And the anonymous rates list - the single most requested resource on the platform, at around 367,000 calls a day - stops taking around 700 milliseconds and starts answering in about six.
One thing did get visibly simpler: signing up. The verification screen after registration is now a single form, instead of a dead end telling you to go check your email.
The rates list answers in milliseconds
The anonymous rates endpoint now serves a pre-rendered response from cache. The full list took 717 milliseconds before; on a cache hit it takes 6.2. The cache refreshes the moment quotes actually update, so the speed costs nothing in freshness, and authorised requests are untouched. The currency list, another endpoint every integration touches on start-up, was rebuilt to stop making several lookups per currency. The response body is unchanged, but arrives sooner.
Deposits that stop waiting
A short interruption of an internal infrastructure component could leave a deposit lock hanging for its full lifetime, and the deposit with it, sitting in Created for up to 30 minutes. The lock is now a self-renewing lease: an orphaned lock is detected and safely released within minutes, and a brief interruption leaves no orphaned lock behind at all.
Sign-up: one form, not a relay
The screen after registration used to be read-only: "Check your email", and the link in that email was the only way forward. It’s now one form with three fields: the code from the email, your password, and its confirmation. Arrive by the link and the code is pre-filled but editable; arrive without it and you can type or paste the code yourself. The separate password step is gone. Verifying the email and setting the password happen in a single submit, and the autofill hints are set so the browser offers the one-time code in the code field and a new password in the password field, not the other way round.
Gram, settled in
The platform renamed Toncoin to Gram at the end of July, and the rename left a handful of rough edges. GRAM currencies show their own icon everywhere, including the older admin panel. Block explorer links resolve. The destination tag field appears where it should.
One of these fixes was worth more than cosmetics. A wallet that activates itself on its first outgoing transaction, which is how Gram wallets work, was shown as Not active, with a live Activate button. Pressing it would have charged a real activation fee to an address that was already active. The status is now confirmed with the node before it’s displayed, and the button is hidden for wallets that are, in fact, active.
Fixes that remove noise
Payout approval events for threshold-based approvals now go only to the users configured as approvers, so an approval request stops landing in inboxes that can’t act on it. Partner program bonuses are trimmed from eighteen decimal places to two. A scam token arriving at a deposit address no longer spawns an automatic duplicate deposit, and every automatically created deposit is logged with System as its initiator, so its origin is never a mystery. Cancelling an unstaking request no longer raises a false incident.
For white-label operators: closing what the node never saw
A payout that the blockchain node never registered used to be closable only through a database change by engineering. It can now be closed from the panel: on the Node info page, a Fail button appears for payouts the node reports as not found, and moving such a payout to a final status always clears its Need review flag. Before failing, the payout is re-checked against the node: a payout that did reach the network can’t be failed by mistake.
AML returns now reconcile with the node. When a node sweeps the entire balance of an address, the refund amount matches what was actually swept, so returns of blocked funds no longer stall on addresses that held uncollected deposits. And address validation for payouts now checks the destination tag or memo alongside the address for currencies that use one (XRP, XLM, GRAM and others). A valid address with an invalid tag is rejected with a structured error instead of slipping through.
The new admin interface keeps filling in. The details pages for deposits, payouts and transfers gained their read-only sections: a deposit’s transactions, a transfer’s node info and last callback, settings and order details. And on white-label platforms, system emails built from the older template set (compliance, transfer, swap and report notifications) now carry the platform’s own branding throughout.
Version 26.2.14 is available now. Log in, or read the full release notes in the documentation.
.svg)
