Yes — the Cryptnox Crypto Hardware Wallet – Dual-Card Set can hold FDUSD as an EVM token on Ethereum, BNB Chain, or Arbitrum after you add the network or token in the Cryptnox app. FDUSD is not pre-programmed on the cards. Use the 0x-prefixed 20-byte EVM address for the supported FDUSD forms. FDUSD on Solana, Sui, and TON is not holdable through this FDUSD route.
CRYPTNOX products are also available worldwide through our official Amazon stores.
FDUSD support on the Cryptnox Crypto Hardware Wallet – Dual-Card Set is support for the EVM token forms of First Digital USD. The holdable routes are FDUSD on Ethereum as ERC-20, FDUSD on BNB Chain as BEP-20/ERC-20-equivalent, and FDUSD on Arbitrum as ERC-20-equivalent. Each supported FDUSD route uses a 0x-prefixed 20-byte EVM address.
First Digital Labs presents FDUSD as First Digital USD, but the name alone is not enough when you are choosing a hardware wallet route. For Cryptnox, the network selected for FDUSD determines whether the token form is holdable. Ethereum, BNB Chain, and Arbitrum are the FDUSD routes to use here; Solana, Sui, and TON FDUSD are not holdable through this setup.
The Dual-Card Set does not arrive with FDUSD already enabled. After initialising the cards, you add FDUSD once through the Cryptnox app by using “Add a Network” or “Add a Token,” depending on the EVM route you need. Before sending funds, check the Cryptnox coin and blockchain support page so the FDUSD network you choose matches Ethereum ERC-20, BNB Chain BEP-20/ERC-20-equivalent, or Arbitrum ERC-20-equivalent.
FDUSD can appear across several chains, so the chain name and address format are the practical buying checks. With Cryptnox, the FDUSD forms you can hold are the EVM routes that use a 0x-prefixed 20-byte address. If a sending service offers a non-EVM FDUSD withdrawal path, that path should not be used for this Cryptnox FDUSD setup.
The supported FDUSD routes share the EVM-style 0x address format, but they are still different network choices at the sending side. Ethereum FDUSD must be sent as ERC-20, BNB Chain FDUSD must be sent through the BNB Chain token route, and Arbitrum FDUSD must be sent through the Arbitrum token route. Do not treat the repeated FDUSD ticker as proof that every chain version belongs at the same address type.
The Binance Academy overview of FDUSD is useful background on the asset, while the transfer decision for Cryptnox remains narrower: select Ethereum, BNB Chain, or Arbitrum when receiving FDUSD to the wallet controlled by the card.
FDUSD is added in the Cryptnox app after the Dual-Card Set has been initialised. The app step matters because this asset is not pre-programmed on the cards. You first prepare the wallet, then add the EVM network or token route that matches the FDUSD you plan to receive.
If you already own the cards and want the setup flow before adding FDUSD, use the Cryptnox hardware wallet tutorials. The tutorial path is especially useful for FDUSD buyers because the token is added after wallet setup, not activated as a factory-loaded asset.
Importing an existing BIP39 recovery phrase is an advanced option. The default FDUSD path for a new Cryptnox wallet is to initialise the two cards, let the wallet material be generated inside both secure elements, and then add the chosen EVM token route before receiving FDUSD.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set ships uninitialised, which is important for a new FDUSD wallet. During setup, the seed is generated inside both secure elements. The second card is therefore the backup for the same FDUSD-capable wallet from the start of the setup flow, and there is no recovery phrase to write down by default.
For FDUSD, the backup is tied to the wallet that controls the 0x-prefixed EVM address used on Ethereum, BNB Chain, or Arbitrum. The token entry can be added in the app, but the underlying wallet backup is the second card created during initialisation. Store that second card separately from the card you use for day-to-day FDUSD approvals.
FDUSD balances may move between services that show the same ticker on different networks. The backup card does not remove the need to choose the correct FDUSD chain, but it does give you a second card for the same wallet when the FDUSD route is one of the supported EVM forms. If you receive Ethereum ERC-20 FDUSD, BNB Chain FDUSD, or Arbitrum FDUSD to the wallet address, the backup card belongs to that same wallet setup.
For FDUSD on Ethereum, BNB Chain, or Arbitrum, the private keys for the 0x-prefixed EVM address are generated inside the secure element and never leave it. The card platform uses an EAL6+-certified chip, and FDUSD transactions are approved without exporting the private keys from the card.
The Cryptnox card itself has no fingerprint or face sensor. Unlock approval uses the phone’s fingerprint or face unlock through the Cryptnox app where the phone supports that method. That distinction matters for FDUSD holders because the phone provides the app interface for selecting the EVM route and reviewing activity, while the card remains the device that protects the keys for the FDUSD address.
The Cryptnox wallet is a contact and NFC smart card. You can tap the card to a phone, or insert it into a reader, when working with the FDUSD wallet through the supported product flow. Buyers looking for an nfc crypto hardware wallet for FDUSD should note that the card is dual-interface, not limited to phone tapping.
The free Cryptnox app is available on iOS and Android for initialising the cards, adding the FDUSD EVM token route, and using the phone as the screen and approval environment. The Swiss-engineered card form is suited to FDUSD buyers who want a physical card controlling an EVM address rather than a browser-only token wallet.
The Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. For FDUSD, this applies to the holdable EVM token forms: Ethereum ERC-20, BNB Chain BEP-20/ERC-20-equivalent, and Arbitrum ERC-20-equivalent. The Web3 connection does not make Solana, Sui, or TON FDUSD holdable with this route.
When connecting FDUSD to Web3 tools, keep the network visible throughout the workflow. A token named FDUSD on Ethereum, a token named FDUSD on BNB Chain, and a token named FDUSD on Arbitrum are separate route choices even though the wallet address format is EVM-style. The Cryptnox card protects the keys for the address; the app and connected tool provide the interface.
If you are choosing a hardware wallet for more than FDUSD, start with the Cryptnox hardware wallet hub and keep the FDUSD decision tied to the three EVM routes listed on this page. Buyers comparing EVM account workflows can also review the Cryptnox Polygon hardware wallet page, while buyers separating FDUSD token storage from Bitcoin storage can use the Cryptnox Bitcoin hardware wallet page.
For portfolios that include other networks as well as FDUSD, keep those decisions separate from the First Digital USD transfer route. The Cryptnox Tron hardware wallet page and Cryptnox Ronin hardware wallet page cover their own asset contexts; this FDUSD page is specifically for Ethereum, BNB Chain, and Arbitrum token forms.
No. FDUSD is not pre-programmed on the Dual-Card Set. After initialising the cards, add FDUSD once in the Cryptnox app by using “Add a Network” or “Add a Token.” The holdable FDUSD routes are Ethereum ERC-20, BNB Chain BEP-20/ERC-20-equivalent, and Arbitrum ERC-20-equivalent.
You can hold FDUSD on Ethereum as ERC-20, on BNB Chain as BEP-20/ERC-20-equivalent, and on Arbitrum as ERC-20-equivalent. These are the EVM token forms supported for this FDUSD route. FDUSD on Solana, Sui, or TON is not holdable with this setup.
Use a 0x-prefixed 20-byte EVM address for the holdable FDUSD forms. That address format applies to FDUSD on Ethereum, BNB Chain, and Arbitrum. Do not use a Solana, Sui, or TON FDUSD address for this Cryptnox FDUSD route.
The Dual-Card Set ships uninitialised. During setup, the seed is generated inside both secure elements, so the second card is the backup for the same wallet. By default, there is no recovery phrase to write down. Store the backup card separately from the card used for FDUSD approvals.
Yes. Cryptnox ships worldwide from the official CRYPTNOX store. Orders to Switzerland, the European Union and the United States are dispatched from stock already held in each of those regions, so the parcel does not cross a customs border into your country and there are no import duties to pay. Orders to other destinations are shipped internationally, and any import duties or local taxes are set by the destination country and are the recipient’s responsibility. Current shipping rates are shown at checkout.
No. For FDUSD on the supported EVM routes, the private keys for the 0x-prefixed address are generated inside the secure element and never leave it. The card platform uses an EAL6+-certified chip, while the Cryptnox app provides the interface for adding and using the token.
Yes. The free Cryptnox app on iOS and Android connects to Web3 through WalletConnect and works with MetaMask. For FDUSD, use those connections only with the holdable EVM token routes: Ethereum ERC-20, BNB Chain BEP-20/ERC-20-equivalent, or Arbitrum ERC-20-equivalent.
No. The Cryptnox wallet is a contact and NFC smart card, so you can tap it to a phone or insert it into a reader. For FDUSD, the phone runs the Cryptnox app and approves unlock with the phone’s fingerprint or face unlock where supported; the card has no fingerprint or face sensor.
No, and on this network that is not a limitation. The Cryptnox wallet uses one address per chain. HD address rotation comes from Bitcoin’s UTXO model and the BIP32/BIP44/BIP49/BIP84 derivation scheme; on account-model networks each account is a single fixed address by design, so the question does not apply in the same way. Cryptnox’s single-address-per-chain behaviour matches how these networks work.
At the cryptography layer the card derives keys along BIP32 and SLIP-10 paths, one path per supported chain, though that is not exposed in the app as multi-address management.