wave.space
wave.space is best understood as a Bitcoin-to-everyday-money bridge for Europeans. Its Nostr relevance is specific: the wavecard can use Nostr Wallet Connect to refill a small card balance from your Lightning wallet, so you can keep most spendable sats outside the card account while still paying at ordinary Visa merchants.
What wave.space really is
wave.space is a Bitcoin banking and card product for Europe. The public site frames the product around one everyday problem: you may want to keep wealth in Bitcoin, but rent, groceries, flights, insurance and most card terminals still settle through fiat rails. wave.space tries to bridge that gap with BTC/EUR swaps, a personal virtual IBAN, a wavecard Visa debit card and Lightning support.
The product is not a Nostr client. You do not open wave.space to publish notes, manage a follow graph or read a feed. You open it to move between Bitcoin and EUR, to receive or send through Lightning and on-chain Bitcoin, to use a debit card, or to connect a Lightning wallet to the card through Nostr Wallet Connect. That distinction matters because the risk profile is closer to an exchange, card issuer and banking app than to a social app.
The company behind the service is Wave Space Exploration UAB, with the footer naming a Lithuanian company registration number and the team page presenting Felix Billert and Eivydas Rackauskas as the two public founders. The site says the company is built from Berlin and Vilnius, while the terms point to Lightspark Payments Europe AS as the regulated partner that provides important financial services. Read the product as a branded application layer sitting on top of partner banking, card, Bitcoin and compliance infrastructure.
Why it belongs under Exchanges
wave.space belongs under Exchanges because its main economic action is conversion. Users can send EUR and receive Bitcoin, send Bitcoin and receive EUR, or fund a card balance that is sold into fiat at the moment of card spending. The site presents this as living on Bitcoin, but the operational layer is still exchange: price, spread, fees, settlement timing, bank account details, KYC and partner availability all matter.
The category should not hide the debit-card shape. The wavecard is the visible product many readers will notice first. It is a Visa debit card that lets a user spend in normal merchant environments while the Bitcoin side is handled behind the scenes. That makes wave.space different from a simple exchange order book, but it does not remove exchange risk. Every card payment becomes a small conversion and authorization event.
The NWC ecosystem also lists wave.space under Exchanges, describing it as a debit-card product with automatic topups powered by NWC. That is the right mental model. The card and IBAN make the product useful in everyday life; NWC is the mechanism that can connect a self-custodial Lightning wallet to the card topup flow.
The card is the sharp edge
The wavecard is the product surface where the promise becomes concrete. The card page says users can spend Bitcoin wherever Visa is accepted, manage cards, freeze cards, change limits, create more cards, set a pseudonymous card name and use contactless payment paths such as Google Pay, Samsung Pay, Fitbit Pay and Garmin Pay. It also explains that Apple Pay support is currently indirect through Curve rather than native.
The card is Bitcoin-first in marketing, but card networks are not Bitcoin-native. A merchant authorizes a fiat card transaction. To make that work, the system needs a funded card balance, conversion pricing, fraud controls, 3-D Secure, issuer rules, partner terms and support. The Auto Topup article is honest about this: Visa needs visible funds to authorize the payment, so the user still keeps some liquidity in the card system.
That is why you should treat the card balance as spending power, not as savings. It may be convenient to keep enough sats on the card for meals, groceries or travel. It is much harder to justify parking long-term Bitcoin there when the same product is designed to let you connect a Lightning wallet and top up only when needed.
NWC Auto Topup in plain terms
Nostr Wallet Connect is the feature that makes wave.space relevant to the Nostr map. The Auto Topup post describes a flow where a user connects a Lightning wallet to the wavecard through NWC, chooses a spending-power threshold, and lets the card refill automatically when spending drops the balance below that threshold. In the example, a card purchase reduces the card balance and NWC replenishes the missing amount from the user's Lightning wallet.
The practical benefit is narrow and important: you do not need to keep all spendable Bitcoin inside the card account. You can keep most of it in your own Lightning wallet and let the card pull small topups when ordinary card spending happens. That is more self-custodial than preloading a large custodial card balance, but it is not the same as paying the merchant directly from your wallet. The card system still needs pre-positioned liquidity for authorization.
The security boundary is the NWC connection. The wave.space article says users can set budgets, recurring limits, expiration times and permissions in the connected wallet, and that the app cannot override those wallet-side settings. Take that seriously. A card topup connection is a spending permission. It should have a low limit, a clear name, a short expiry if possible and a wallet balance that matches your real card-risk tolerance.
How NWC actually fits
NWC is not a bank API and not a card network standard. It is a Nostr-based protocol for letting an app request Lightning wallet actions over relays. The NWC documentation explains the user-facing idea: an app connection is created, a wallet confirms it, and the app can request payment actions through a relay according to the permissions granted by the wallet.
For wave.space, that means the card product can talk to a Lightning wallet without holding the user's Lightning node keys. The app does not need the private key of the wallet. It needs a connection secret and wallet permissions that allow the topup behavior. NIP-47 defines the broad message model, while NIP-04 is still relevant because the published NIP-47 specification uses encrypted request and response messages.
This makes the feature interoperable in a way card products usually are not. A reader can connect a wallet such as Alby Hub if it supports the needed NWC permissions and budget controls. The downside is also interoperability: each wallet, relay path and mobile or server runtime behaves differently. Before you make the card a daily tool, test the exact wallet, NWC limit, relay reliability, background behavior and topup timing with tiny payments.
Buying Bitcoin with EUR
The buy page presents wave.space as a direct way to buy Bitcoin from a euro bank account. A user creates an account, verifies basic information, sends EUR from a bank account and receives BTC that can be spent with wavecard or withdrawn to an external wallet. The page emphasizes direct wallet use and a simple one percent fee, with a small liquidity-provider spread shown elsewhere in the site.
The February 2026 product update adds an important feature called Link. Link gives a selected wallet a dedicated IBAN after the user whitelists the wallet and approves the flow. After that, euro deposits sent to that IBAN can become Bitcoin sent to the chosen wallet automatically. That is useful for recurring purchases, but it makes wallet whitelisting and destination control more important.
If you use the buy flow, test the destination first. A direct-to-wallet purchase is only as good as the address or Lightning destination you provide. Keep records of the EUR transfer, the quoted price, the fee, the spread, the Bitcoin transaction or Lightning receipt and the withdrawal destination. The product may make buying feel like normal banking, but the Bitcoin side is still final once sent.
Selling Bitcoin into EUR
The sell page describes the reverse path: send BTC from a wallet, have it swapped to EUR, then receive the EUR through SEPA Instant to a bank account. wave.space repeatedly emphasizes that transfers use a virtual IBAN in the user's own name, which may reduce the account-freeze problems that some users experience when receiving transfers from obvious exchange accounts.
The flow can use on-chain Bitcoin, Lightning, NWC or wave.space itself according to the site's sell page. That variety is useful, but it also means the user must know which rail is actually being used. On-chain Bitcoin has confirmation time and network fees. Lightning has invoice expiry, route liquidity and wallet availability. NWC adds permission and relay assumptions. The bank payout depends on SEPA Instant and partner services.
Selling Bitcoin is not a privacy escape hatch. The service requires verification, partner terms apply, and the privacy policy describes collection and sharing of personal data for service, compliance and partner purposes. The bank may see a transfer from an account in your own name, but wave.space and its partners still know the account, customer and transaction context.
The virtual IBAN is useful, not magic
A personal virtual IBAN is central to the product story. It gives the user a euro account-like destination for transfers into and out of the Bitcoin system. The homepage and FAQ material position it as a stable link between Bitcoin and ordinary bank life: deposits can be converted to BTC, withdrawals can arrive as EUR and transfers appear under the user's own name.
That can be genuinely useful in Europe, especially for people who want to avoid repeated exchange withdrawal friction. It also changes the trust boundary. A virtual IBAN is provided through partner infrastructure, not through a decentralized protocol. Terms, availability, compliance checks, supported countries, account reviews and partner limitations decide whether it works for you.
Use the IBAN like a regulated financial account. Confirm the name, address, country eligibility, transaction limits, transfer references, support process and tax reporting expectations. A recurring buy setup through Link may be convenient, but a misconfigured destination or closed account can turn convenience into a support case.
Fees and limits to verify
The current public terms list a one percent conversion fee for crypto-to-euro and euro-to-crypto swaps. For wavecard, they list a physical-card issuance fee of EUR 29.99, tracked delivery at no additional fee, express delivery at EUR 30, virtual-card issuance at EUR 2.99, a one percent card payment fee and ATM cash withdrawals at EUR 2 plus three percent. The card page also discusses an approximate 0.5 percent liquidity-provider spread in the BTC price.
The card FAQ lists daily card spending of EUR 10,000, monthly card spending of EUR 10,000 with up to EUR 15,000 at a higher KYC tier, daily ATM withdrawals of EUR 350 and monthly ATM withdrawals of EUR 3,000. The buy and business pages mention up to EUR 100,000 transaction sizing in their own contexts. These figures are useful, but they are not a substitute for the live app and terms at the moment you transact.
Check the fee stack before using the card abroad. wave.space says it does not add foreign-exchange fees between fiat currencies and that users get fair rates, but a card payment can still include Bitcoin conversion, liquidity spread, issuer behavior, merchant category constraints, ATM fees, weekend or network effects and refund conversion differences. For small everyday spending this may be acceptable; for large purchases, quote first.
Partner infrastructure matters
The terms say licensable financial services are provided by Lightspark Payments Europe AS. They also say partner services include user euro accounts, virtual IBANs, crypto accounts, Visa debit cards and trading or exchange services. The linked partner terms identify Lightspark Payments Europe AS in Estonia and describe virtual asset services, vIBAN accounts, supported networks and risk notices.
This partner structure is normal for fintech, but readers should not ignore it. wave.space is the product and customer-facing brand; Lightspark and other third-party providers may be the entities behind the regulated account, card, trading, exchange or service layer. If something goes wrong, the answer may depend on which part of the stack failed.
Before you rely on the product, open the Wave Space terms and the linked partner documents. Look for restrictions, supported countries, prohibited uses, customer due diligence, service availability, complaints, account closure, withdrawal fees, card terms and data roles. A card app can look simple while the legal structure underneath is several documents deep.
KYC and privacy reality
wave.space is not a no-KYC privacy wallet. The card page says KYC is needed to provide a personal virtual IBAN and the wavecard in Europe. The terms require account registration and accurate information, and the privacy policy describes personal data collection from users, automatic website data and third-party sources. It also distinguishes between Wave Space acting as data controller for some processing and data processor for partner-led processing.
The pseudonymous card-name feature should not be misunderstood. It may let you set a merchant-facing name on the card, which can reduce casual exposure in some card contexts. It does not mean the company, partner providers or compliance stack do not know who you are. A pseudonymous card is not the same as anonymous financial infrastructure.
For Nostr users, this is a familiar but important separation. NWC can protect wallet keys and limit app permissions. It does not erase KYC, card-network data, bank-transfer metadata, device data, support records or legal retention duties. Use compartmentalization: separate wallet connections, low balances, clear records and no assumption that a card product gives the privacy of direct peer-to-peer Bitcoin.
Refunds, chargebacks and 3-D Secure
Card products have edge cases that Lightning wallets do not. The terms say card refunds are converted back to BTC at the available market rate and without extra service cost from wave.space. That sounds helpful, but it still means a refund can come back at a different Bitcoin price than the purchase. If you buy a refundable flight, hotel or subscription, the Bitcoin result can differ from the euro face value you remember.
The card setup asks users to keep recovery codes and set a 3-D Secure password. The Apple Pay workaround article also warns that Curve can trigger checks, that billing-address mismatch can cause problems, and that 3-D Secure authorization can be required for verification. These are ordinary card-world details, but they matter when your funding source is Bitcoin.
Test card controls before you travel. Freeze and unfreeze the card. Change a limit. Make a tiny online purchase. Try a small in-person contactless payment. Confirm how 3-D Secure appears on your phone. Check what happens if the NWC topup cannot run. The time to learn the failure mode is not at a hotel desk or supermarket checkout.
Business use is a different lane
wave.space also presents a business product for companies that want to buy, hold, accept and spend Bitcoin while staying inside a compliant account flow. The business page mentions business onboarding, corporate virtual IBANs, instant BTC/EUR swaps and the ability to hold Bitcoin in a business account or withdraw to self-custody.
That is related to the consumer card, but it should not be evaluated with the same checklist. A company needs accounting, authority controls, treasury policy, invoice records, employee card rules, tax treatment, source-of-funds documentation, customer-payment treatment and an internal decision on whether Bitcoin sits in self-custody or a business account.
If you run a business, ask for the exact terms, supported countries, onboarding requirements, transaction limits, API availability if any, export formats, signatory controls and support commitments. The one percent fee line is only one part of the decision. Operational controls decide whether the product is useful beyond a founder's personal card.
The February 2026 product shift
The February 2026 update is worth reading because it shows wave.space moving from a narrow swap-and-card product toward a broader web app that feels closer to a Bitcoin neobank. The post mentions a redesigned interface, faster navigation, passwordless login, Link, Lightning addresses, smarter transaction grouping, search and filters.
Lightning addresses are particularly relevant for ordinary users because invoices are awkward. The update says users can claim a free wave.space address and that adding a euro-oriented suffix can auto-convert received BTC to EUR. That is a neat convenience feature, but it also means readers should understand whether a received payment remains Bitcoin, becomes EUR, lands in a card balance or goes to an external wallet.
The product is therefore evolving. Old blog posts, roadmap labels and current app behavior may not line up perfectly. Before publishing wallet instructions to friends, employees or community members, check the live app and current docs. A feature can move from early access to production, change limits or gain new KYC requirements without old articles disappearing.
Not all self-custody claims are equal
wave.space uses self-custody language because it can connect to external Bitcoin wallets and because NWC lets card topups pull from a Lightning wallet without giving wave.space wallet keys. That is a meaningful improvement over a card that requires a large custodial preload. It lets you reduce the amount inside the card account.
But the final card purchase is still not a direct Lightning payment to the merchant. The merchant is paid through Visa rails. The user keeps a small card balance available as spending power. The app or partner stack converts Bitcoin into fiat settlement. The NWC wallet may refill the card after spending. This is a hybrid system, not a pure non-custodial wallet.
The right question is not whether the marketing word is allowed. The right question is how much money sits in each trust zone: your own wallet, the NWC permission, the card balance, the partner crypto account, the virtual IBAN and the merchant authorization path. Keep the high-value zone under your strongest control and let the card zone stay small.
What to test before relying on it
Begin with the smallest practical amounts. Open the account, complete verification, create one virtual card, set a low limit, buy or deposit a tiny amount of Bitcoin, make one small card payment and inspect the transaction details. Then sell a small amount of Bitcoin into EUR and confirm how quickly the bank payout arrives through your own bank.
Then test NWC. Create a dedicated wallet connection named for wave.space, set a daily or recurring budget, set an expiration if your wallet supports it, and keep a small wallet balance. Connect it to wavecard Auto Topup, choose a spending-power threshold and make a card payment small enough that a failed topup would not matter. Afterward, inspect the wallet, relay behavior, card balance, fee and app history.
Finally test recovery and control. Freeze the card. Revoke the NWC connection. Check whether the card can still spend with existing balance. Confirm 3-D Secure, support contact, transaction export, tax record, refund handling and what happens if you change phones. A product meant for daily life deserves a daily-life test, not only a successful signup.
Who wave.space is for
wave.space is a strong fit for European Bitcoin users who already think in Bitcoin but still need ordinary EUR and card rails. If you want to buy groceries, pay online, receive or send bank transfers, sell BTC for rent, or keep a small card balance fed by a Lightning wallet, the product addresses a real pain point.
It is less suitable for readers seeking no-KYC privacy, long-term storage, jurisdiction-free payments or a fully decentralized spending path. The product lives in the regulated European fintech world. It can make Bitcoin easier to use there, but it also inherits the costs: verification, partner documents, card rules, account review, data processing, tax responsibility and service downtime.
Use it in the lane it was built for: everyday spending and BTC/EUR bridging with clear limits. Keep long-term savings elsewhere. Use NWC to reduce card exposure, not to create an unlimited drain from your wallet. Treat the card as a convenience surface and your wallet policy as the real safety system.
The practical close
wave.space matters because it takes NWC out of the demo-app corner and puts it into a very concrete payment problem: how can a person spend from a Lightning wallet in ordinary Visa environments without preloading a large custodial card balance? The answer is not perfect, but it is useful: keep a small spending-power balance on the card, refill it through a permissioned NWC connection and keep most spendable Bitcoin in a wallet you control.
The careful reader should believe the promise and the caveats at the same time. wave.space is one of the clearer examples of NWC becoming payment infrastructure outside the Nostr social client world. It is also a regulated card and exchange product with KYC, partner terms, fees, spreads, bank rails, card limits, refund mechanics and data processing. Those are not footnotes. They are the product.
If you try it, do it like an operator. Start small, document the fee math, set wallet limits, keep the card balance low, test failure cases and know how to revoke the connection. In that shape, wave.space can be a practical bridge between self-custodial Lightning and daily European spending, without pretending that a Visa card has become a Bitcoin wallet.
Sources worth opening
Open the current wave.space homepage, wavecard page, buy and sell pages, terms, privacy policy, the Auto Topup post, the February 2026 product update and the partner documents linked from the terms. Then compare the awesome-nwc listing, NWC documentation, NIP-47, Alby's NWC context and Lightning invoice material.
