Adding funds to your urble wallet
Your wallet can receive funds two ways.
Option 1: Receive crypto from another wallet: if you already hold BTC, ETH, ADA, or a supported stablecoin (like ZCHF, USDC, or EURC on the Ethereum network) in another wallet, you can send it directly on-chain. Open Receive in your urble wallet, pick the asset/network, and either share the address or let the sender scan your QR code. Double-check the network matches — sending an unsupported asset or using the wrong network can result in permanent loss of funds.
Option 2: Add funds by bank transfer: to convert CHF or EUR from a bank account into crypto, use "Receive via bank account." This shows personalized transfer instructions from our partner (currently DFX): an amount, an IBAN, a BIC, and a Message code, plus a dropdown to choose which crypto asset the incoming CHF/EUR should be converted into. This requires identity verification first — see How to Complete Identity Verification (KYC) with Our Partners if you haven't done that yet. Exact fees for the conversion are always shown in the transfer estimator before you confirm.
One detail that trips people up: the Message field. Whatever text urble shows you there must be copied exactly into your eBanking when you prepare the transfer — it's how our partner matches your incoming payment to your account. Banks label this field differently: Message, Purpose of Payment, Reference, or Note to Recipient are all common names for the same freely-editable field. Don't confuse it with the structured reference number field used for QR-bill payments in Switzerland — that's a different, fixed-format field, and it's not the one you want here.
Setting up a bank transfer as a standing order
Any bank transfer to your wallet can be set up as a recurring standing order in your eBanking, as long as it's always converting into the same crypto asset. Just use the same IBAN, BIC, and Message shown in the app, and set your bank's standing order frequency to match. If you ever want to change which asset you're buying, you'll need a new set of instructions (and a new standing order) for that asset.
Contributing directly to a savings plan
Beyond the main wallet, each savings plan you set up has its own funding options — useful if you want contributions to go straight into a specific goal rather than sitting in your wallet first. From a savings plan, select your contribution method:
From your urble wallet — if you already have funds in your wallet, contribute directly from there. There's no fee for this (except for blockchain transaction fees). If your wallet doesn't have enough, urble tells you and points you to top up or use a bank transfer instead.
From an external wallet — same idea as the main wallet's crypto receive, but scoped to this specific savings plan: you get a dedicated QR code and address, and the plan only accepts the asset it was set up with (for example, a ZCHF stable-yield plan only accepts ZCHF).
Via bank transfer — works exactly like the wallet-level bank transfer, with one important difference: the Message code is unique to this savings plan. That's what routes your incoming CHF/EUR into this specific plan instead of your general wallet. If you have multiple savings plans, each one has its own Message — don't reuse one plan's details for another.
Standing orders into a savings plan
If you set up a plan with, say, a monthly contribution frequency, you can mirror that with a monthly standing order in your eBanking using that plan's specific bank details. This is the cleanest way to actually follow through on a savings plan without having to remember to transfer each month manually — just make sure the Message code matches the plan you intend to fund.
Confirming your money arrived
Every time a bank transfer or standing order executes, our partner emails you to confirm the CHF/EUR was received and the corresponding crypto asset was delivered. You can also check directly in the app: a savings plan shows successful contributions right in its activity feed, and your wallet shows each incoming transaction under the relevant asset's transaction history.
