Cryptnox supports PYUSD only as a token on supported EVM networks: Ethereum ERC-20, Arbitrum One, Polygon PoS, and X Layer. PYUSD is not pre-programmed on the card; after setup, add the relevant network or token in the Cryptnox app. The PYUSD route uses an 0x-prefixed 20-byte EVM address, and the private keys for that address are generated inside the card secure element and never leave it.
CRYPTNOX products are also available worldwide through our official Amazon stores.
PayPal USD, PYUSD, can be held with the Cryptnox Crypto Hardware Wallet – Dual-Card Set when the asset is used on supported EVM networks. The supported PYUSD holding route for this card setup is Ethereum ERC-20, Arbitrum One, Polygon PoS, or X Layer. The Solana SPL and Stellar representations are different PYUSD routes and are not the holding route described for this page.
PYUSD is not shipped as a ready-made asset entry on the card. The Dual-Card Set ships uninitialised, then the buyer creates the wallet during setup and adds the PYUSD route in the Cryptnox app by adding the relevant network or token. Once added, the PYUSD address shown for these supported routes is an EVM address: an 0x-prefixed 20-byte address.
Paxos lists PYUSD across Ethereum, Arbitrum One, Polygon PoS, X Layer, Solana, and Stellar. For a Cryptnox buyer, the key distinction is that this page covers the EVM versions only. Before sending PYUSD to the card-controlled wallet address, the sending side should match one of the supported EVM networks named here.
For a broader view of networks and assets, use the Cryptnox coin and blockchain support page before moving PYUSD from another wallet, exchange, or app.
A PYUSD address in this Cryptnox setup is an 0x-prefixed 20-byte EVM address. That format applies when PYUSD is held on Ethereum, Arbitrum One, Polygon PoS, or X Layer. The asset name alone is not enough, because PYUSD also exists on non-EVM routes where the address format is not the EVM format described here.
The address shown in the Cryptnox app must match the PYUSD network used by the sender. If the sender offers Ethereum, Arbitrum One, Polygon PoS, or X Layer for PYUSD, the address format is the EVM route covered here. If the sender is using Solana SPL PYUSD or Stellar PYUSD, that is a separate representation and should not be treated as the same address route.
The Cryptnox hardware wallet tutorials are useful during setup because PYUSD requires the correct route to be selected rather than assumed from the asset name.
The Dual-Card Set ships uninitialised, so PYUSD is not already enabled when the cards arrive. First, the wallet is created during setup. After that, PYUSD is added in the Cryptnox app for one of the supported EVM networks. This setup path keeps the route clear: initialise the cards, select the EVM network needed for PYUSD, then add the asset entry used for that network.
This matters because the same asset name appears on multiple chains. PayPal’s help page describes PayPal USD, but the Cryptnox setup still depends on the network route used for holding it. With Cryptnox, the supported PYUSD holding route is limited to the EVM networks named on this page.
The product sold for this setup is the Cryptnox Crypto Hardware Wallet – Dual-Card Set. The set provides the smart cards; PYUSD itself is added by the buyer in the app after initialisation.
For PYUSD on Ethereum, Arbitrum One, Polygon PoS, or X Layer, control of the asset depends on control of the private key for the 0x-prefixed EVM address. With Cryptnox, that private key is generated inside the secure element and never leaves it. The key used for the PYUSD address is not created outside the card and then copied into it by default.
The card platform uses an EAL6+-certified chip. That property applies to the chip platform, not to a finished card as a whole. For a PYUSD holder, the practical point is that the EVM address used for PayPal USD is controlled by a key created and kept inside the smart card secure element.
Unlocking happens through the Cryptnox app using the phone’s face or fingerprint check. The card itself has no biometric sensor. In a PYUSD workflow, the phone provides the app interface for selecting the asset route and unlocking access, while the private key for the EVM address remains inside the card secure element.
Buyers comparing custody across asset types can see the same key-control approach on the Cryptnox Bitcoin hardware wallet page, while the PYUSD route here remains specific to EVM-token holding.
The Cryptnox Crypto Hardware Wallet – Dual-Card Set creates the PYUSD wallet setup with two smart cards. During initialisation, the seed is generated inside both secure elements, so the second card is the backup for the same wallet. In the default setup, the buyer does not have to write down a recovery phrase to create the PYUSD backup.
For PYUSD, the backup card controls the same EVM wallet setup used for Ethereum, Arbitrum One, Polygon PoS, or X Layer. The backup is not a separate PYUSD address and it is not a second token setup. It is the second card for the same wallet created during initialisation.
Buyers who also hold EVM assets can compare this backup model with the Cryptnox Polygon hardware wallet page, where the same card-based product family is used for another EVM network route.
The Cryptnox wallet is a contact and NFC smart card, which matters for PYUSD because the asset is added and managed through the app while the card remains the key holder. You can tap the card to a phone, or insert it into a reader. The form factor is dual-interface, so it is not limited to one contact method.
The free Cryptnox app is available on iOS and Android. For PYUSD, the app is where the buyer adds Ethereum, Arbitrum One, Polygon PoS, or X Layer as needed, views the 0x-prefixed EVM address, and uses the phone’s face or fingerprint check for unlocking. The card has no biometric sensor; the phone handles that part of the app flow.
The app connects to Web3 via WalletConnect and works with MetaMask. For PYUSD holders, that means the supported EVM address controlled by the card can be used through those connection methods. WalletConnect and MetaMask do not change the PYUSD routes supported here: the holding route remains Ethereum ERC-20, Arbitrum One, Polygon PoS, or X Layer.
If you are choosing by asset or network, the Cryptnox crypto hardware wallet hub groups related hardware wallet pages. For comparison with a different network page, see the Cryptnox Tron hardware wallet page.
Cryptnox is a fit for buyers who want to hold PayPal USD on Ethereum, Arbitrum One, Polygon PoS, or X Layer while keeping the private key for the EVM address inside a smart card secure element. It is also a fit for buyers who want the backup to be a second card created during setup, rather than a written recovery phrase in the default flow.
The key decision is the PYUSD route. If the PYUSD you plan to receive is on an EVM network covered here, the Cryptnox app can be set up for that network and the asset can be added after the cards are initialised. If the PYUSD is the Solana SPL or Stellar representation, it is not the route described on this page.
Cryptnox is Swiss-engineered and uses a contact and NFC smart card design. For this PYUSD setup, the buyer gets a card-based way to control an 0x-prefixed EVM address, with private keys generated inside the secure element and kept there. For another asset page in the same product family, the Cryptnox Ronin hardware wallet page shows how network-specific support is handled for a different route.
Yes. Cryptnox supports PYUSD on Ethereum ERC-20, Arbitrum One, Polygon PoS, and X Layer. PYUSD is not pre-programmed on the card, so you add the needed EVM network or token in the Cryptnox app after the Dual-Card Set is initialised.
For the supported PYUSD routes, Cryptnox uses an 0x-prefixed 20-byte EVM address. That applies to PYUSD on Ethereum, Arbitrum One, Polygon PoS, and X Layer. The Solana SPL and Stellar representations use different routes and are not the PYUSD holding route covered here.
No. The Dual-Card Set ships uninitialised, and PYUSD is not pre-programmed on the card. After setup, you add the relevant EVM network or PYUSD token in the Cryptnox app. The supported choices for this page are Ethereum, Arbitrum One, Polygon PoS, and X Layer.
This PYUSD page covers the EVM representations only: Ethereum ERC-20, Arbitrum One, Polygon PoS, and X Layer. PYUSD also exists as an SPL token on Solana and as an issued asset or token on Stellar, but those are separate representations from the route described here.
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.
For the supported EVM PYUSD routes, the private key controlling the 0x-prefixed address is generated inside the secure element and never leaves it. The card platform uses an EAL6+-certified chip. Unlocking uses the phone’s face or fingerprint check through the Cryptnox app.
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 PYUSD wallet setup. By default, there is no recovery phrase to write down; importing an existing BIP39 recovery phrase with 12 or 24 words is an advanced option.
The free Cryptnox app on iOS and Android connects to Web3 via WalletConnect and works with MetaMask. For PYUSD, this applies to the supported EVM routes on Ethereum, Arbitrum One, Polygon PoS, and X Layer, using the 0x-prefixed address controlled by the card.
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.