Skip to main content
NFT credentials is a credential group setting. When it is on, every credential you publish in the group is also minted as an NFT (a non-fungible token) on Hedera, a public blockchain. Hyperstack keeps the NFT safe until the recipient claims it to their own wallet, such as HashPack or MetaMask. The credential itself does not change. Recipients still get the same email, credential page and wallet. The NFT is an extra, public proof that they hold the credential.
NFT credentials is an add-on. Contact us to turn it on for your organization. You need the Credential issuer or Administrator role to change a group.

​
Turn on NFT credentials

1

Open the group

Go to Credential Groups and click the group. For a new group, click Create group.
2

Open the Security settings

Under More settings, click Security.
3

Set NFT credentials to Enabled

The row then reads NFT credentials on.
4

Save the group

Click Update group, or Create group for a new group.
The Security settings of a credential group with NFT credentials enabled
New groups start with it disabled. To turn it off, set NFT credentials to Disabled and save the group.

​
What happens when you publish

  1. You publish credentials as usual. Publishing is as fast as before: it does not wait for the NFTs.
  2. In the background, Hyperstack mints one NFT for each credential. A single credential is usually minted in under a minute. A large group takes longer, for example about an hour for 10,000 credentials.
  3. Each NFT stays in the Hyperstack vault until its recipient claims it.
If Hedera does not answer, Hyperstack tries again on its own. A failed mint never stops a credential from being published. Your organization gets its own NFT collection on Hedera, named after your organization. It is made the first time you mint.

​
What goes on the blockchain

Only the link to the public credential page goes into the NFT. Names, email addresses, titles and other credential data do not. The credential page shows the design and the details, as it does today.

​
Existing credentials

Only credentials that you publish after you turn on the setting get an NFT. Credentials that you published before do not.

​
How recipients claim the NFT

The recipient signs in to their wallet. The credential card reads NFT ready to claim.
Two credential cards in the wallet: one with the NFT in the recipient's wallet, one with the NFT ready to claim
They open the claim form, paste their wallet address and click Claim NFT:
  • A Hedera account ID, for example 0.0.4455667 (HashPack and other Hedera wallets).
  • An EVM address that starts with 0x (MetaMask and other Ethereum-style wallets).
The Claim your NFT dialog with a Hedera account ID in the Wallet address field
The NFT reaches the wallet within seconds. Some wallets ask the recipient to accept a new NFT before it shows.
  • Each credential’s NFT can be claimed once.
  • Only the recipient of the credential can claim it.
  • The NFT cannot be sent on to another wallet. It stays with the recipient, like the credential.

​
What verifiers see

On the credential page, the Credential Authenticity section shows two more rows:
  • NFT: the collection ID and the NFT number, for example 0.0.5129874 · #18. Click it to open the NFT on HashScan, a public Hedera explorer.
  • NFT status: In the Hyperstack vault before the recipient claims it, then Claimed.
The Credential Authenticity section with the NFT and NFT status rows, status Claimed
The credential page never shows the recipient’s wallet address. When the recipient views their own credential, the page also shows Claim it to your wallet while the NFT is in the vault.
The credential page for the recipient, with the NFT in the Hyperstack vault and a Claim it to your wallet link

​
When you revoke or delete a credential

Hyperstack removes the NFT from the blockchain:
  • If the recipient has not claimed it, the NFT is burned.
  • If the recipient has claimed it, the NFT is taken back from their wallet and removed.
When you suspend a credential, the NFT stays. The credential page shows that the credential is suspended.

​
If the add-on ends

  • Hyperstack stops minting new NFTs at once.
  • NFTs that already exist stay. Recipients can still claim them, and they are still removed if you revoke the credential.
  • The NFT credentials setting is hidden from the group form.

​
Technical details

  • Network: Hedera mainnet, using the Hedera Token Service (HTS).
  • Collection: one non-fungible token per organization. Hyperstack holds the supply, freeze and wipe keys.
  • NFT metadata: the URL of the public credential page.
  • Non-transferable: after the NFT reaches the recipient’s account, Hyperstack freezes that account for the collection, so the NFT cannot be sent on.
  • Delivery: a Hedera token airdrop. If the wallet has no free slot for a new token, the airdrop waits until the recipient accepts it in the wallet.
Last modified on November 10, 2026