Yes. The Cryptnox Crypto Hardware Wallet – Dual-Card Set can hold USDD after you manually add the correct route: TRC-20 on Tron, ERC-20 on Ethereum, or BEP-20 on BNB Chain. USDD is not pre-programmed on the cards. Choose the chain that matches your USDD, add the network or token once in the free Cryptnox app, then use the card set to sign while private keys remain inside the secure element.

USDD on Cryptnox is a manual-token setup, not a pre-loaded asset profile. That matters because USDD can be held through three different routes on this product: as a TRC-20 token on Tron, as an ERC-20 token on Ethereum, or as a BEP-20 token on BNB Chain. The correct choice is the route on which your USDD already exists or the route the sender will use.
A buyer should decide the USDD network before receiving funds. TRC-20 USDD belongs to Tron addressing, where the receiving address is a base58 address that begins with T. ERC-20 USDD on Ethereum and BEP-20 USDD on BNB Chain use 0x-prefixed 20-byte EVM addresses. The two EVM routes share the same address shape, but they are still different networks.
You can compare this setup with broader asset coverage on the Cryptnox coin and blockchain support page. If your USDD is on Tron, the related hardware wallet for Tron guide gives chain-specific context for the T-address route.
The USDD ticker alone is not enough to choose a receiving address. A TRC-20 transfer on Tron must go to the Tron route, while ERC-20 and BEP-20 transfers must go to their respective EVM routes. The Cryptnox app lets you add the network or token once, but the route you add must match the token standard used by the sender, exchange, or application.
Use the Tron route when the asset is identified as USDD on Tron or TRC-20 USDD. The receiving address is a base58 T-address. A 0x address is not the address format for this route, even if the token name is the same.
Use the Ethereum route for ERC-20 USDD and the BNB Chain route for BEP-20 USDD. Both routes use a 0x-prefixed 20-byte EVM address, so the selected network becomes the deciding detail. A 0x address on Ethereum and a 0x address on BNB Chain can look similar, but the USDD token route is not interchangeable.
Before entering contract details for a manual add, match the chain to the official USDD deployment information. The USDD deployment address documentation lists deployment addresses by network, which is the right reference point when adding TRC-20, ERC-20, or BEP-20 USDD.
USDD setup in the Cryptnox app starts after the card set has been prepared. Because USDD is not pre-programmed, you add the asset route yourself through Add a Network or Add a Token. Add it once for the chain you need, then use that route when receiving or signing USDD transactions.
The free Cryptnox app runs on iOS and Android. For USDD, its role is to let you prepare the Dual-Card Set, add the selected Tron, Ethereum, or BNB Chain route, and review the transaction flow before the card signs. Unlocking uses the phone’s face or fingerprint check through the app; the card itself has no face or fingerprint sensor.
For product setup walkthroughs before adding USDD, use the Cryptnox hardware wallet tutorials. If you are still comparing card-based wallets before choosing an asset route, the Cryptnox hardware wallet hub explains the product category.
When you set up USDD on the Dual-Card Set, the signing key for the relevant Tron or EVM address is created inside the secure element and stays there. For TRC-20 USDD, that key controls the Tron T-address used for the token route. For ERC-20 or BEP-20 USDD, that key controls the 0x EVM address used on Ethereum or BNB Chain.
The card uses an EAL6+-certified chip. That chip is the secure platform used for key generation and signing, while the finished card remains a contact and NFC smart card. For USDD, the practical result is that the phone or Web3 connection can prepare a transaction request, but the private key is not exported to handle the request.
The form factor also affects daily USDD use. You can tap a card to a phone when using the Cryptnox app, or insert a card into a reader. This dual-interface design is useful for a token such as USDD because the same asset may be used through a mobile flow, a WalletConnect flow, or a MetaMask-related EVM flow depending on whether you are using Tron, Ethereum, or BNB Chain.
Cryptnox connects to Web3 via WalletConnect and works with MetaMask. For USDD on Ethereum or BNB Chain, that gives an EVM connection path after the relevant route has been added. The connection can carry the request, and the card set handles the signing step for the address tied to your USDD route.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set ships uninitialised. During initial setup, the seed is generated inside both secure elements, so the second card is the backup for the same USDD-capable key material. There is no recovery phrase to write down by default when preparing the set for a new USDD wallet route.
This backup model matters differently for each USDD path. If you add TRC-20 USDD, both cards correspond to the same Tron key path used to control the T-address route. If you add ERC-20 or BEP-20 USDD, both cards correspond to the same EVM address route used on Ethereum or BNB Chain. Re-adding a token view in the app is separate from the underlying key material created during setup.
Importing an existing 12- or 24-word BIP39 recovery phrase is an advanced option. The default new-wallet flow for USDD is to initialise the two cards together, let both secure elements generate the seed, and then add the TRC-20, ERC-20, or BEP-20 USDD route you intend to use.
The most important USDD receiving habit is to check chain, standard, and address format together. A Tron T-address only fits the TRC-20 route. A 0x-prefixed address fits the EVM address format used by ERC-20 USDD on Ethereum and BEP-20 USDD on BNB Chain, but the matching network still has to be selected.
When receiving from an exchange or another wallet, use the label shown by the sender. If the sender offers USDD on Tron or TRC-20, use the Tron route. If the sender offers Ethereum, use ERC-20. If the sender offers BNB Chain, use BEP-20. Do not treat the USDD name as a substitute for the network choice.
USDD publishes live asset information at usdd.io/data. Use that for USDD-specific data, and use the deployment documentation when you need to confirm the contract details for a manual token add.
USDD is one manually added token route inside the Cryptnox card setup. The same buyer may also hold assets that use different chain rules, so the USDD page should be treated as route-specific guidance rather than a general token template. USDD requires a choice among Tron, Ethereum, and BNB Chain before the first transfer.
If your next asset is on another network, the address assumptions may change. A Polygon asset uses its own network context, so the hardware wallet for Polygon guide is the better starting point for Polygon routing. If you are comparing with a non-token asset path, the hardware wallet for Bitcoin guide covers a different model from USDD’s TRC-20, ERC-20, and BEP-20 routes.
The common Cryptnox element across those choices is the card-based key model. For USDD specifically, that key model is applied to either a Tron T-address or a 0x EVM address, depending on the route you add. The asset-specific decision remains the same every time you handle USDD: choose TRC-20, ERC-20, or BEP-20 before receiving.
To hold USDD with Cryptnox, buy the Dual-Card Set and add the correct USDD route during setup and use. The product is a Swiss-engineered contact and NFC smart card set, with cards made in Switzerland. You can tap a card to a phone or insert it into a reader, so the same set can serve mobile app use and card-reader use.
For USDD, the buying decision should include the manual-token step. The card set does not arrive with USDD already enabled. After initialising the two cards, add USDD as TRC-20 on Tron, ERC-20 on Ethereum, or BEP-20 on BNB Chain. Then verify the address format before sending a test transfer or sharing a receiving address.
If your goal is USDD on Tron, expect a base58 T-address. If your goal is USDD on Ethereum or BNB Chain, expect a 0x-prefixed EVM address on the selected network. The Cryptnox app, WalletConnect, and MetaMask give the connection paths for using the configured route while the card set remains the signing device for the private key created inside the secure element.
No. USDD is not pre-programmed on the cards. After setting up the Dual-Card Set, add USDD manually through Add a Network or Add a Token in the Cryptnox app. The supported USDD routes are TRC-20 on Tron, ERC-20 on Ethereum, and BEP-20 on BNB Chain.
Choose the network that matches the USDD you will receive or already hold. Use Tron for TRC-20 USDD with a base58 T-address. Use Ethereum for ERC-20 USDD with a 0x-prefixed EVM address. Use BNB Chain for BEP-20 USDD with a 0x-prefixed EVM address on BNB Chain.
ERC-20 USDD on Ethereum and BEP-20 USDD on BNB Chain both use 0x-prefixed 20-byte EVM addresses, but the network still matters. Add and use the route that matches the transfer network. A similar-looking address format does not make Ethereum and BNB Chain USDD the same route.
The private key for the USDD route you use is generated inside the card secure element and never leaves it. The card uses an EAL6+-certified chip for that secure platform. The app or Web3 connection can prepare the USDD transaction request, while the card performs the signing step.
The Dual-Card Set is prepared with both cards during initial setup. The seed is generated inside both secure elements, so the second card is the backup for the same Tron or EVM route you later use for USDD. There is no recovery phrase to copy by default.
Yes. The free Cryptnox app on iOS and Android connects to Web3 via WalletConnect and works with MetaMask. For USDD, first add the correct TRC-20, ERC-20, or BEP-20 route. Then use the connection path required by the service you are using.
No. The card has no fingerprint or face sensor. Unlocking uses the phone’s face or fingerprint check through the Cryptnox app. For USDD transactions, the phone helps with the app unlock and transaction flow, while the card remains the signing device.
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.
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.