Bitvavo expands trading tools, recurring buys and Ethereum transfer routes

What changed in the June update

Bitvavo’s 2 June 2026 product update announced leverage of up to five times on more than twenty assets for eligible users, a simpler short-selling flow and Stop Market orders on Bitvavo Pro. Recurring Buy gained daily purchases across thirty assets. The release also added Base and Arbitrum routes for ETH deposits and withdrawals, one-step Convert swaps across more than two hundred assets, improved tablet and foldable layouts, and more detailed notification controls. These changes address different tasks rather than forming one mandatory trading workflow.

A stop trigger is not a promised sale price

Bitvavo’s order documentation explains that a stop trigger activates an order. A Stop Limit then respects a specified price boundary but may remain unfilled if the market moves beyond it. A Stop Market instead seeks execution at the prices available after activation, which can differ from the trigger. That difference is called slippage.

There is an interface caveat in the help page: it says a market stop can be achieved through a One-Cancels-Other arrangement rather than a standalone order, while its instructions also mention selecting Stop Market. Because the documentation is not completely consistent, the June announcement should not be treated as a precise map of every current account screen. The live order ticket establishes which configuration an eligible user can actually place.

Follow a falling-price example

Imagine an invented holding of ten units bought at fifty euros each. Its original cost is five hundred euros before fees. The holder chooses a trigger at forty-eight euros. If a market-style sale eventually fills at forty-seven euros, the proceeds are four hundred seventy euros before costs. The loss is thirty euros, not twenty, because the final execution price is one euro below the trigger.

Now consider a different fictional instruction with the same trigger but a sell limit of forty-seven euros fifty. If buyers are available only at forty-seven after the trigger, that price is below the permitted boundary. The hypothetical order cannot simply ignore its own limit to obtain the immediate exit. The holder may retain exposure while waiting. The example illustrates two different priorities: bounding execution price and obtaining an exit.

Neither choice makes the price move predictable. The important design step is to decide which result would be less acceptable in the actual plan: an execution below the hoped-for price, or continuing to hold after the threshold was crossed. A person who enters numbers without deciding that may discover only during a fast move that the selected instruction answers the wrong question.

A daily purchase changes the schedule, not the budget automatically

Consider another invented plan intended to spend three hundred euros during a thirty-day month. Ten euros each day reaches that amount if all thirty purchases execute. Ten euros each week would be a very different plan, and three hundred euros each day would multiply the intended budget dramatically. Frequency and purchase amount must therefore be read together.

The number of units acquired can also change from day to day. A ten-euro purchase at two euros per unit gives five units before costs; at two euros fifty it gives four. Across those two illustrative purchases, twenty euros buys nine units, for an average cost of approximately two euros twenty-two per unit. Averaging the two quoted prices would give two euros twenty-five and would not describe this equal-spending example correctly.

Match each update to the job it solves

A person who wants to move existing ETH has a transfer problem; a person who wants to change one asset into another has an exchange problem. Selecting a new network route does not itself swap the asset, just as selecting an asset conversion does not establish that the result has arrived in an external wallet. A clear intended destination prevents those operations from being confused.

The June package is easiest to evaluate one task at a time. In the examples above, the stop instruction controls how a planned exit is attempted, while the recurring instruction controls when new purchases are attempted. Device layouts and notification preferences affect how the person supervises those actions. Using several features together can be convenient, but each should still have a specific purpose and an observable result.