Yes. Cryptnox supports sUSD as an ERC-20 token on Ethereum after you add the token once in the Cryptnox app. sUSD is not pre-programmed on the card. Use the Ethereum contract address 0x57Ab1ec28D129707052df4dF418D58a2D46d5f51 and manage it with a 0x-prefixed Ethereum address. Private keys are generated inside the secure element and never leave it, while Web3 access runs through WalletConnect and works with MetaMask.
CRYPTNOX products are also available worldwide through our official Amazon stores.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set can hold sUSD through the Ethereum ERC-20 route. The card set does not arrive with sUSD already enabled; you add sUSD once in the Cryptnox app as an Ethereum token.
The sUSD token contract is 0x57Ab1ec28D129707052df4dF418D58a2D46d5f51. Etherscan identifies 0x57Ab1ec28D129707052df4dF418D58a2D46d5f51 as the sUSD contract on Ethereum, which is the contract address to use when adding the token.
For a buyer who wants to hold sUSD, the critical point is the relationship between the Ethereum address and the token contract. The Cryptnox card secures the private key for the Ethereum address. The token entry tells the app which ERC-20 balance to display for that address.
The Cryptnox coin and blockchain support page is useful when checking sUSD alongside Ethereum assets, because sUSD is handled as an ERC-20 token rather than as its own separate chain.
sUSD is added in software after the card set has been prepared. Open the free Cryptnox app on iOS or Android, use the Add a Network or Add a Token flow, and enter the Ethereum token details for sUSD.
The token symbol alone is not the setup item to rely on. ERC-20 tokens are identified by contract address, so the contract 0x57Ab1ec28D129707052df4dF418D58a2D46d5f51 is the important entry. Once the token has been added, the app can show the sUSD ERC-20 balance for the Ethereum address controlled by the card.
The card is not being changed into an sUSD-only device when you add the token. The card protects the Ethereum private key; the app records the sUSD token entry for display and transaction preparation.
For the card and app sequence around setup, the Cryptnox hardware wallet tutorials give the product workflow, while the sUSD-specific entries are Ethereum, ERC-20, the 0x address format, and the contract address above.
sUSD on Cryptnox is controlled through an Ethereum private key. With the Cryptnox Crypto Hardware Wallet – Dual-Card Set, private keys are generated inside the secure element and never leave it.
The card uses an EAL6+-certified chip. That certification applies to the chip platform. For an sUSD holder, the relevant security model is that the Ethereum private key is created and kept inside the secure element instead of being stored as an ordinary app secret.
The sUSD token contract identifies the ERC-20 token. The Ethereum private key controls the 0x-prefixed address that can hold the token. If you add the correct sUSD contract but use the wrong Ethereum account, the token balance belongs to the account tied to that address, not to the token entry itself.
Cryptnox separates those roles. The app can show sUSD and prepare interactions. The card remains the place where key generation and key retention occur. When you hold sUSD, the valuable secret is the Ethereum private key, and that key stays inside the secure element.
Unlocking uses the phone’s biometrics through the Cryptnox app. The card itself has no biometric sensor. The card remains a contact and NFC smart card, while the phone provides the unlock experience through the app.
This setup is especially relevant for sUSD because adding the token is simple, but the protection decision is about the Ethereum key behind the 0x address. The token entry can be added in the app; the private key is not exported from the secure element.
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 Ethereum address structure that can hold sUSD.
This matters for sUSD because the ERC-20 balance is attached to an Ethereum address. The token contract identifies sUSD, but the seed controls the Ethereum account. When the Dual-Card Set is initialised in its default route, both cards are tied to the same seed generated inside their secure elements.
The default routine avoids beginning with a paper recovery phrase. For a buyer who plans to hold sUSD, that means the backup is the second smart card rather than a phrase written down during normal setup.
The backup card is not a separate sUSD account. It corresponds to the same seed generated during initialisation, which means it relates to the same Ethereum address structure used for the sUSD ERC-20 token entry.
The Cryptnox card is a contact and NFC smart card. You can tap it to a phone or insert it into a reader. That dual-interface format gives the card two ways to be used with the Cryptnox app and supported reader workflows.
The free Cryptnox app is available on iOS and Android. In the sUSD flow, the app is where you add the Ethereum ERC-20 token, use the phone’s biometrics to unlock, and connect to Web3 through WalletConnect.
Cryptnox connects to Web3 via WalletConnect and works with MetaMask. For sUSD, the account context remains Ethereum: the token is ERC-20, the receiving address begins with 0x, and the token contract is 0x57Ab1ec28D129707052df4dF418D58a2D46d5f51.
When a Web3 service asks for an Ethereum wallet connection, the sUSD balance is tied to the Ethereum account controlled by the card. WalletConnect provides the connection route, while the secure element keeps the private key inside the card.
The card itself has no biometric sensor. If you unlock through the app, the phone supplies the face or fingerprint check, and the card remains the hardware key device for the Ethereum account that can hold sUSD.
The product for holding sUSD with this setup is the Cryptnox Crypto Hardware Wallet – Dual-Card Set. Choose it when you want sUSD held through an Ethereum address whose private key is generated inside a secure element and backed up by a second card.
The buying decision is not about receiving a card with sUSD preloaded. The buying decision is whether the Ethereum ERC-20 route fits your sUSD holding plan: initialise the two cards, add the sUSD token contract once, and use the app to view and interact with the token.
The cards are Swiss-engineered. The relevant purchase fit for sUSD is the combination of Ethereum ERC-20 token addition, secure-element key generation, and the two-card backup model.
If you want the broader product-family context before ordering, the Cryptnox hardware wallet hub explains the card-wallet category around the Dual-Card Set.
sUSD in this setup is an ERC-20 token on Ethereum. Use the Ethereum token contract and a 0x-prefixed Ethereum address. Do not treat the sUSD entry as a separate chain inside the card.
This matters before receiving or moving sUSD, because the token entry and the account address must match the Ethereum context. The card protects the private key for the Ethereum address, and the app displays the sUSD balance associated with the ERC-20 contract.
If you also manage TRON assets, use the separate TRON hardware wallet page for that network instead of applying the sUSD Ethereum contract route to TRON.
If you also manage Polygon assets, the Polygon hardware wallet page covers that network context, while sUSD here remains tied to the Ethereum ERC-20 contract 0x57Ab1ec28D129707052df4dF418D58a2D46d5f51.
A Bitcoin address model is different from an Ethereum ERC-20 token entry, so use the Bitcoin hardware wallet page when planning Bitcoin storage. If you also hold RON, the Ronin hardware wallet page is the relevant place for that asset route.
For sUSD itself, keep the setup narrow and precise: Ethereum network, ERC-20 standard, 0x-prefixed address, and the sUSD contract address.
No. sUSD is not pre-programmed on the card. You add it once in the Cryptnox app as an ERC-20 token on Ethereum. Use the contract address 0x57Ab1ec28D129707052df4dF418D58a2D46d5f51 and manage it through an Ethereum address that begins with 0x.
Choose Ethereum for this sUSD setup. sUSD is held as an ERC-20 token on Ethereum, and the receiving address uses the 0x-prefixed 20-byte EVM address format. The token contract identifies sUSD, while the Ethereum address is controlled by the private key generated inside the secure element.
Enter 0x57Ab1ec28D129707052df4dF418D58a2D46d5f51 for sUSD on Ethereum. The contract address is the setup detail that distinguishes the ERC-20 token from other token symbols. Use it when adding sUSD through the Add a Network or Add a Token flow in the Cryptnox app.
The Dual-Card Set ships uninitialised, and the seed is generated inside both secure elements during setup. The second card is therefore the backup for the same Ethereum address structure that can hold sUSD. The backup relationship follows the seed and Ethereum account, not the visible token label.
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. The card itself has no biometric sensor. Unlocking uses the phone's biometrics through the Cryptnox app. The card remains a contact and NFC smart card, so it can be tapped to a phone or inserted into a reader.
Yes. The free Cryptnox app connects to Web3 through WalletConnect and works with MetaMask. For sUSD, keep the network context as Ethereum and the token standard as ERC-20. The card secures the Ethereum private key while the app handles token display and Web3 connection.
Yes, importing an existing BIP39 recovery phrase is available as an advanced option. It is not the default route for the Dual-Card Set. By default, the cards ship uninitialised and the seed is generated inside both secure elements, making the second card the backup.
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.