A New Wallets Page, Verified Payout Addresses and a Wallet API

The Wallets page has been rebuilt, payout addresses are now checked before they are saved, and everything on the page can be done through the API, including the wallet lock.

A cleaner Wallets page

The Wallets page shows every coin you can accept in one list, with its network and payout address.

• At a glance: how many coins you accept and whether your addresses are locked
• Search and filter by coin or network, or show only the coins that are on or off
• One editor for every coin, with the network named in the address field so a USDT address goes on the right chain
• Clear errors that keep what you typed, instead of sending you back to an empty form
• Copy buttons next to each saved address
• A layout that works on your phone, with each coin as a card

Every payout address is verified

A typo in a payout address can send money somewhere nobody can reach. Each address now goes through two checks before it is saved:

• Format and checksum for the coin’s network, so a mistyped or truncated address is caught straight away
• A live check with the payment network, the same one every invoice uses. Burn addresses and token contract addresses are refused, even when they look valid

If the network refuses an address, you see the reason and nothing is saved. Addresses you already saved keep working.

Manage wallets through the API

Merchants who rotate payout addresses asked for this. You can now do it from a script:

• GET /api/v1/wallets lists every coin with its address, whether it is on, and the lock status
• PUT /api/v1/wallets/{coin} sets an address, turns a coin on or off, or both. The same two checks apply
• POST /api/v1/wallets/lock locks your addresses for 1 to 365 days

A new address applies to new invoices only. Every invoice address keeps forwarding to the payout address that was set when the invoice was created, including any payment sent to it later.

Wallet access is off by default

A key that can change payout addresses could redirect your payments if it ever leaked. So reading wallets works with any key, but changing them needs Wallet access turned on for that key on the API Keys page. It is off for every key, including the ones you already have. Only turn it on for a key that stays on a server you control.

The wallet lock can only be extended

Once you lock your addresses, nobody can lift the lock early, including WolvPay support. You can extend a lock from the dashboard or the API, but not shorten it. A shorter request leaves the current lock as it is. A monthly rotation looks like this: when the lock ends, set your new addresses, then lock for another 30 days.

What you need to do

Nothing, unless you want to automate your wallets. The full reference is in the docs and in openapi.json. Questions are welcome on Discord.