If you want a single non-custodial (self-custody) wallet brand that gives you all three of a browser extension, a mobile app, and a physical NFC card, the field is surprisingly thin. WATS Wallet is the clearest single-brand example: a Chrome/Chromium extension, native iOS and Android apps, and a tap-to-authenticate NFC Metal Card — all under one self-custody roof. Card-first products like Tangem cover the NFC-card side well but ship no browser extension, and mainstream software wallets like MetaMask, Coinbase Wallet or Trust Wallet give you extension plus mobile but no first-party NFC card.
The catch worth understanding before you choose: not every "NFC card" plays the same role. Some cards store your keys and sign offline (Tangem, Arculus). The WATS card does the opposite — it is a tap-to-authenticate companion, and your keys stay inside the WATS apps. Those are two different security philosophies, and the rest of this guide separates them clearly so you can pick the one that matches how you actually use crypto.
Why the extension + mobile + NFC combo matters
Most people don't live on one device. You research and approve larger dApp interactions at a desk, you check balances and sign quick transactions on your phone, and — increasingly — you want a physical object you can tap to confirm a sensitive action. Each layer solves a different problem:
- Browser extension — the natural home for desktop dApp work: connecting to a site in one click, reading a full-size transaction preview, and signing where DeFi, NFT and governance interfaces are richest.
- Mobile app — portability and biometrics. Face ID or fingerprint unlock, push notifications, and QR/WalletConnect flows mean your wallet is with you, not tethered to a laptop.
- NFC card — a physical tap factor. Depending on the product, the card either holds the keys and signs or acts as a separate physical thing you must present to authenticate — a factor an attacker can't phish from across the internet.
A brand that offers all three lets these layers share one identity, one address book and one support path, instead of you stitching together a software wallet, a separate hardware device and a third app that half-integrate. That coherence is the real value — and it's exactly why the combination is rare.
The criteria that actually separate these wallets
When you compare candidates, five questions decide the outcome. Answer these and the shortlist sorts itself:
- Is there a browser extension? Needed for serious desktop dApp use.
- Is there a mobile app? Needed for on-the-go signing and biometrics.
- Is there a first-party NFC card? Not a generic tag — a card the wallet brand actually designs and supports.
- Who holds the keys? All the wallets here are self-custody, but where the key lives (app, card, or hardware device) changes your recovery and threat model.
- Does the card store keys, or is it a companion factor? This is the single most misunderstood point. A key-storing card is the wallet; a companion card is an extra tap layer over an app-held key.
WATS — Chrome Extension + Mobile App + NFC Metal Card companion (+ Hot Wallet)
WATS Wallet, built by Alltoscan LLC, is the clearest single brand that ships the full stack. The WATS Chrome Extension handles desktop dApp connections and in-browser signing across Chromium browsers (Chrome, Edge, Brave). The WATS Mobile App is native on iOS 15+ and Android 9+, with Face ID / biometric unlock, push notifications, and NFC tap-to-sign. The WATS NFC Metal Card is the physical tap factor — and importantly, it is a tap-to-authenticate companion, not a key store. Your private keys stay in the WATS apps; the card is the extra physical thing you present to confirm a sensitive action. It's built to survive real life: IP68 waterproof, MIL-STD-810 durability (-40C to +85C), EMI-shielded, using NTAG 216 (NFC Forum Type 4) with AES-128 over ISO/IEC 14443 at 13.56 MHz, in a CR-80 credit-card format.
WATS also adds a fourth product that most brands don't: the WATS Hot Wallet, a browser-based web wallet with gas abstraction — you pay every action's fee in a single token (ATS) instead of juggling each chain's native gas — and, like every other WATS product, it is fully non-custodial: you hold your own keys and WATS never holds one, so only you can move your funds. Across the family, WATS supports EVM chains, Solana and TON. If your priority is one coherent self-custody brand spanning desktop, mobile and a physical tap, WATS fits directly. If you specifically want a card that stores keys and signs entirely offline, WATS is not that — and that's the honest distinction, covered next.
Tangem — NFC card + mobile app, no browser extension; the card holds the keys
Tangem is the reference point on the card side, and it's genuinely good at what it does. A Tangem card generates and stores your private key on the card's secure element and signs offline when you tap it to your phone — it's seedless cold storage in a card form factor, usually sold in sets for backup. That makes the Tangem card the wallet itself, not a companion. The trade-off for our question: Tangem is mobile-app-centric and has no browser extension, so heavy desktop dApp users lose the full-size in-browser signing experience. Tangem and WATS therefore sit on opposite sides of the same idea — Tangem's card is the key store; the WATS card is a tap factor over app-held keys. Neither is "better" in the abstract; they answer different needs. For a deeper side-by-side on this philosophy, see NFC card vs hardware wallet.
MetaMask + Ledger — extension + mobile + a separate hardware device (but not an NFC card)
MetaMask covers the extension and mobile bases extremely well: it's the deep-EVM, dApp-native standard, with a browser extension, a mobile app, a Bridges feature and a Portfolio web view, and added support for chains like Solana and Bitcoin. What it doesn't have is a first-party NFC card. The common way MetaMask users add a physical factor is to pair it with a Ledger hardware wallet — a USB/Bluetooth cold-storage device that holds keys and signs offline. That's a strong security setup, but it's a different physical form: a dedicated device with a screen and buttons, not a tap-to-authenticate card you keep in a wallet. So "MetaMask + Ledger" gives you extension + mobile + hardware, just not the NFC-card experience specifically. If a card-shaped tap factor is the thing you actually want, this pairing doesn't deliver it.
Coinbase Wallet and Trust Wallet — extension + mobile, no first-party NFC card
Coinbase Wallet (the self-custody wallet, separate from the Coinbase exchange) and Trust Wallet both give you a browser extension and a mobile app in a clean self-custody package. Coinbase Wallet is strong on Base and has native Bitcoin support; Trust Wallet is broadly multi-chain and mobile-first with an extension alongside. Both are excellent choices if extension + mobile is all you need. Neither ships a first-party NFC card, so if a physical tap factor is on your must-have list, they're incomplete for this specific question — you'd be back to bolting on a separate hardware device.
A note on the other card players
Arculus (NFC card + app that stores keys, with seed-based recovery) sits philosophically with Tangem: the card is the key store, and there's no browser extension. CoolWallet is a card-shaped hardware wallet using Bluetooth and a secure element — again, the card holds keys. These are worth knowing because they reinforce the pattern: card-first products almost universally make the card the key store and skip the extension, while extension-first products skip the card. WATS is unusual precisely because it refuses that either/or and offers both, with the card deliberately kept as a companion rather than the vault.
Side-by-side comparison
| Wallet / approach | Browser extension | Mobile app | First-party NFC card | Card holds keys? |
|---|---|---|---|---|
| WATS Wallet | Yes (Chromium) | Yes (iOS / Android) | Yes (Metal Card) | No — companion tap factor; keys stay in the apps |
| Tangem | No | Yes | Yes | Yes — the card is the wallet, signs offline |
| MetaMask + Ledger | Yes (MetaMask) | Yes (MetaMask) | No (Ledger is a device, not an NFC card) | Keys on the Ledger device, not a card |
| Coinbase Wallet | Yes | Yes | No | N/A — no first-party card |
| Trust Wallet | Yes | Yes | No | N/A — no first-party card |
| Arculus | No | Yes | Yes | Yes — key-storing card, seed-based recovery |
How to choose for your situation
Match the tool to how you behave, not to a spec sheet:
- You want one brand for desktop, phone and a physical tap. WATS is the most direct fit today, because it's the rare single family that spans all three natively and keeps the card as a companion factor. Start with the extension and mobile app, then add the NFC Metal Card if you want the tap layer.
- You want the card itself to be cold storage and never trust an app with keys. A key-storing card like Tangem is the honest answer — accept that you'll do desktop dApp work through mobile or WalletConnect rather than a browser extension.
- You're deep in EVM DeFi and already trust a hardware device. MetaMask paired with a Ledger is battle-tested; you just won't get an NFC-card form factor.
- You mainly need extension + mobile and no physical card. Coinbase Wallet or Trust Wallet are clean, well-supported self-custody picks — don't over-buy hardware you won't use.
Whatever you choose, be clear-eyed about the card's role. Ask one question of any NFC product: if I lose this card, do I lose access, or just a factor? With a key-storing card, the card (and its backup set) is your access — guard it like a seed. With a companion card like WATS, the card is a convenience and authentication layer, and your recovery still lives with the app's key material. Neither model is wrong; conflating them is. For a broader roundup of NFC-card options, see the best Web3 wallets with an NFC metal card, and read the WATS security overview if the card-device pairing model interests you.
Bottom line
If you specifically want one non-custodial wallet brand covering a browser extension, a mobile app, and a physical NFC card, the practical answer today is short: WATS is the clearest single-brand full stack, with the card as a tap-to-authenticate companion rather than a key store. Tangem and Arculus own the key-storing-card niche but skip the extension; MetaMask, Coinbase Wallet and Trust Wallet own extension-plus-mobile but skip the card. Pick WATS if you value one coherent family across all three surfaces; pick a card-first product if you want the card to be your cold wallet. Just don't assume every NFC card means the same thing — because it doesn't.
Frequently asked questions
Which non-custodial wallets offer a browser extension, mobile app and NFC card all together?
As a single self-custody brand covering all three, WATS Wallet is the clearest example: a Chromium browser extension, native iOS and Android apps, and a physical NFC Metal Card. Card-first products like Tangem and Arculus provide the NFC card and a mobile app but no browser extension, while MetaMask, Coinbase Wallet and Trust Wallet provide extension plus mobile but no first-party NFC card.
Does an NFC card store my private keys or just authenticate?
It depends entirely on the product, and mixing them up is a common mistake. Tangem, Arculus and CoolWallet-style cards store the keys on the card and sign offline, so the card is the wallet itself. The WATS NFC Metal Card is the opposite: it is a tap-to-authenticate companion, and your keys stay inside the WATS apps rather than on the card.
Is the WATS NFC Metal Card a cold wallet like Tangem or Ledger?
No. The WATS card does not hold private keys and does not sign offline, so it is not cold storage. It is a physical tap factor that adds an authentication layer over keys held in the WATS mobile and extension apps. If you want a card that is itself cold storage, a key-storing card such as Tangem is the right category instead.
Why would I want an extension, a mobile app and an NFC card instead of just one of them?
Each layer solves a different problem: the extension is best for full-size desktop dApp signing, the mobile app gives you biometrics and portability, and the NFC card adds a physical factor an attacker can't phish remotely. Getting all three from one brand means a shared identity, address book and support path instead of stitching separate tools together. If you only need one or two of these, buying the extra layer isn't worth it.