Overview

HID Approve handles access requests and transaction signing from a mobile device. Consumer applications include approving payments, signing banking transactions, meeting Strong Customer Authentication workflows, and securing financial-service logins. Workforce uses include VPN and remote access, corporate and cloud applications, and regulated workflows.

Organizations can deploy a customizable mobile app or integrate authentication into their own applications with an SDK. The approach offers flexibility for teams building their own user experience, while the SDK connects to ActivID Authentication Server, ActivID Appliance, or HID Authentication Service. That makes it a more natural fit for organizations already using or prepared to adopt those components than for teams seeking a standalone authenticator.

Key features

Authentication and signing

Push notifications, QR-code authentication, and one-time passwords cover several approval patterns. Users can authenticate access requests and sign transactions on mobile. HOTP and TOTP codes also work offline, an important fallback where connectivity is unavailable, though offline operation applies to the one-time-password method.

Integration and administration

The HID Authentication Service exposes a REST API for managing device types, credential types, and authentication policies. Team administration, directory sync, and authentication policies support workforce deployments; read-event analytics and movement history add operational visibility. The integration story is substantial, but its value depends on fitting the organization’s existing identity architecture.

HID describes the product as using standards-based cryptography and says it is backed by third-party penetration testing and independent audit reviews. HID states support for PSD2 and Open Banking, EPCS, PCI-DSS, and GDPR-related requirements. These statements may help regulated buyers assess suitability, but organizations should verify that the specific deployment meets their obligations.

Pricing

HID Approve is paid, with custom pricing. The single HID Approve plan covers consumer and workforce authentication with mobile-app or SDK deployment. There is no free plan, and no trial, seat allowance, quota, or renewal term is stated; buyers should request a quote and confirm scope and commercial terms before selecting it.

Platforms

The product supports Android and iOS mobile apps, with API integration and Windows and macOS support. HID also lists a standalone .NET installer for Windows. The broader operating-system footprint includes Linux, but the core deployment choices described are a customizable mobile app or SDK integration.

Who it's for

HID Approve is suited to banks, financial-service providers, and employers that need mobile transaction approval or workforce authentication, especially where HID’s ActivID or Authentication Service is part of the intended architecture. Teams needing offline OTP capability or a choice between a vendor app and embedded SDK have concrete reasons to consider it.

It is less compelling for individuals or small teams seeking a free authenticator, or organizations that want hardware security keys rather than mobile authentication. Those buyers should compare tools built around those needs.

Pros and cons

Pros: Push, QR, and OTP methods accommodate different approval flows; offline OTP provides a fallback when a device lacks internet access.
Pros: Mobile-app and SDK deployment options let organizations choose between a customizable app and integration into an existing application.
Pros: REST API access, directory sync, policies, analytics, and movement history address administration as well as authentication.
Cons: Custom pricing and no free plan make it a procurement-led choice rather than an easy low-cost trial.
Cons: SDK integrations rely on specified HID authentication platforms, so teams outside that ecosystem should assess integration fit before committing.
Cons: Offline support is described for OTP, not for push or QR approval flows.

Alternatives

For a free, open-source authenticator that requires a YubiKey to store credentials and generate them, consider Yubico Authenticator. For hardware-key approaches, compare Deepnet SafeKey, TrustKey T110, Swissbit iShield Key 2, Nitrokey 3, and Solo 2; Nitrokey 3 and Solo 2 are described by their makers as open source.

If a mobile OTP product is the priority, SafeNet MobilePASS+ and FEITIAN Mobile Authenticator are alternatives. For broader category browsing, see Security Keys, Authenticator apps, RFID Software, and Passkey Authentication Software.

Verdict

Choose HID Approve when mobile transaction signing or workforce approvals must fit into an HID-backed authentication stack, and when the organization values SDK integration, multiple authentication methods, and offline OTP. Look elsewhere if a free authenticator or hardware key is the primary need, or if the required HID service integration does not fit the stack.

	Dipole LAMA Middleware	HID Approve
Free plan	No	No
Free trial	No	No
Paid from	—	—
Open source	No	No
Platforms	Web, Windows	Android, api, iOS, macOS, Windows
Deployment	on-premises	cloud
Read-event analytics	Yes	Yes
Movement history	Yes	Yes
Exception alerts	Yes	—
API access	Yes	—

Dipole LAMA Middleware vs HID Approve

Dipole LAMA Middleware

HID Approve