Choosing a SafeID hardware token depends on your Identity Provider's support for multi-factor authentication seed uploads.

Selecting between Pre-Programmed and Programmable Hardware Tokens for MFA

The following tables help show how the two types of hardware tokens are prepared, and used, when accessing a protected application:

Your Primary Goal

Recommended Token Type

Recommended SafeID Models

Deploy to large teams on Microsoft Entra ID (P1/P2), Okta, or Cisco Duo with zero user setup.

Pre-Programmed TOTP TokensSafeID/Classic, SafeID/Enterprise

Use hardware tokens on Microsoft Entra ID Free without paying for P1/P2 add-on licenses.

Programmable TOTP TokensSafeID/Diamond, SafeID/Pro

Authenticate legacy on-premises VPNs or RADIUS gateways requiring counter-based codes.

Pre-Programmed HOTP Tokens

SafeID/Eco


The following table lists the full range of these tokens (and their key features):

Token TypeProductKey Features

Pre-Programmed Hardware Tokens (Factory-Seeded)

Choose pre-programmed tokens when you want hardware authenticators that work straight out of the box with zero end-user setup. Your IT administrator uploads a factory-supplied seed file into your identity platform (such as Microsoft Entra ID, Okta, or Cisco Duo), assigns a serial number to each employee, and hands them the device.

The pre-programmed lineup delivers a 5–7 year battery life (3–5 years for audio and card models) and supports both TOTP and HOTP protocols across rugged keyfob, slim card, and ADA-compliant audio form factors.

  • Explore the full lineup: See our Pre-Programmed Hardware Tokens guide for side-by-side product specs, SHA-256 compliance models, and seed-file formats (CSV and PSKC/XML).

SafeID/Enterprise & SafeID/Classic

Durable TOTP keyfobs for standard enterprise and remote staff.

SafeID/Mini

Ultra-compact TOTP keyfob (41 x 19 x 6 mm) for crowded keychains.

SafeID/Anytime

Button-less TOTP keyfob with a continuously displayed 6-digit code.

SafeID/Audio

ADA Section 508-compliant TOTP keyfob that speaks codes aloud for visually impaired users.

SafeID/Eco

Event-based (HOTP) keyfob for legacy VPNs featuring a replaceable battery.

SafeID/Classic Card

Wallet or lanyard friendly credit card form factor (TOTP, 4–5 year battery).

Programmable Hardware Tokens (NFC & USB Flashable)

Choose programmable tokens when your platform blocks bulk seed-file uploads—or when you want to avoid expensive enterprise licensing tiers (such as Microsoft Entra ID P1/P2). They act as physical replacements for smartphone authenticator apps (like Google or Microsoft Authenticator) and can be provisioned in seconds by scanning a standard QR code via NFC or USB.

The programmable lineup delivers a 3–7 year battery life and supports single-account keyfobs, multi-account PIN-protected tokens (up to 10 or 100 accounts), and slim credit-card designs.

  • Explore the full lineup: See our Programmable Hardware Tokens guide for side-by-side model comparisons, NFC/USB programming requirements, and multi-seed capacity details. 

SafeID/Pro & SafeID/Diamond

Single-account TOTP keyfobs serving as physical smartphone authenticator replacements (5–7 year battery).

SafeID/PinPad (Pro)

Multi-account keyfob (up to 10 accounts) with an optional hardware PIN lock.

 SafeID/QR (Pro)

High-capacity keyfob (up to 100 accounts) powered via USB that displays codes numerically or as QR codes.

SafeID/Diamond Card & SafeID/Diamond Card Mini

Credit card and compact footprint options storing 1 account with a 3–5 year battery life.

TOTP vs. HOTP: Choosing the Right Security Protocol

These days most applications that provide OTP authentication will provide access either by hardware tokens, or authentication apps, and whilst a few providers may require event based tokens (HOTP) , the majority will use time based tokens (TOTP).

If HOTP is required, then the SafeID/Eco token will be a natural choice, but in most cases (such as Microsoft), most providers will require TOTP tokens, and the choice will then come down to pre-programmed or programmable tokens.

As can be seen in the decision tree below, the selection between these two types mostly depends upon if seed file uploading is supported:



Many major service providers will allow uploading of seed files, but for those that do not, the vast majority will allow the use of authentication apps (and our programmable tokens can act as direct drop-in replacements for these apps)

Does Your Application Support Hardware Tokens ?

Using Pre-Programmed Tokens with Unsupported Apps (DualShield SAML Bridge)

Using Programmable Tokens

Frequently Asked Questions (FAQ)

Can I use SafeID hardware tokens with Microsoft Entra ID Free?

Yes, via Programmable SafeID Tokens. While Entra ID requires a P1 or P2 license to bulk-upload CSV seed files, you can deploy programmable TOTP tokens (SafeID/Diamond, SafeID/Pro) on the Microsoft Entra ID Free tier by registering them as app-based authenticators.

What equipment do I need to program a SafeID token?

Can a programmable SafeID token be reset?

Yes. Unlike factory-locked pre-programmed tokens, programmable models can be overwritten with a new QR code or secret key if an employee transitions or changes accounts.

How long do SafeID hardware token batteries last?

Most keyfob models (SafeID/Classic, SafeID/Enterprise, SafeID/Pro, SafeID/Diamond) last 5 to 7 years. Slim card models last 3 to 5 years, and the SafeID/Eco includes a user-replaceable battery.

What if my application doesn't support OATH seed file uploads?

  1. Use a Programmable SafeID Token to clone the platform's standard MFA QR code.
  2. Route authentication through Deepnet DualShield via SAML 2.0 to use pre-programmed tokens.

Related Articles