BSV Wallet Toolbox 2.15.3 Fixes Rejection of Some Confirmed Payments

Developer Tools, Latest News, Wallets & Identity

Developer Tools / Wallets & Identity

In Brief

Wallet Toolbox 2.15.3 fixes a problem that could make a wallet reject an incoming payment even after it had been confirmed on BSV Blockchain. Published on November 5 (UTC), the update is available to wallet developers and service operators.

News Report

Wallet Toolbox is software developers use to build BSV wallets. Version 2.15.3 is now available in its core, client and mobile packages. Users benefit as their wallet providers adopt and deploy the update.

Why a Confirmed Payment Could Be Refused

When a wallet receives a payment, it also needs information that lets it verify and record that payment. The affected process uses AtomicBEEF—a package containing the payment transaction and supporting information needed to check it.

Some older sending software can include unrelated transaction records in that package. The receiving wallet’s initial format check could reject the package before its existing cleanup process ran. That could prevent even a confirmed payment from completing the normal import process.

What Version 2.15.3 Changes

The update handles that specific failure by removing unrelated transaction records, preserving the original payment and the records it depends on, and running the usual checks again.

The payment’s transaction ID and contents remain unchanged. Checks of the supporting blockchain proof, spending conditions and the recipient’s ownership still apply. The accompanying regression tests cover successful cleanup and continued rejection of incomplete or malformed packages.

What Operators Need to Update

Wallets that use a separate storage service need to consider both the wallet software and that service when updating. The project’s notes call for separate upgrades, with no change to the public interface or database structure.

For a previously rejected payment, the guidance is to check the wallet’s records against the original transaction ID before retrying the import. Recovery uses the existing payment; it does not require the sender to pay again.

BSV TIMES Read

Compatibility is part of payment reliability. Different wallet teams update at different times, so valid payments need to survive those differences while retaining the checks that protect the recipient. This release addresses one such mismatch. Its practical reach will depend on adoption by wallet providers.

Developer Context

Brayden Langley authored the compatibility fix. He is also a coauthor, alongside Ty Everett and Tone Engel, of BRC-100, the standard interface through which BSV applications communicate with wallets.

Source Links

Posted on November 6, 2026 (UTC)