Documentation Home

Choose a documentation area to get started.

Getting StartedSet up and begin working with the HID components.Release NotesReview version changes, improvements, and fixes.Product LifecycleUnderstand supported versions and lifecycle information.HID Components OverviewExplore the Web and Mobile component catalogue and workflows.

HID Components Overview

A unified guide to the HID Temenos Digital web and mobile components, their primary responsibilities, and the onboarding and login journeys available for each authentication choice.

Scope. This guide consolidates the supplied authentication, user-management, transaction-signing, mobile-component, and Infinity workflow documentation. It focuses on the component capabilities and user journeys relevant to web and mobile banking implementations.

Guide Overview

The component set supports user authentication, onboarding, device lifecycle management, and transaction authorization across web and mobile channels. The exact screens and factors shown are controlled by the selected component properties and configured authenticators.

Web channel

Authentication

Mobile channel

HID Approve SDK

Onboarding, PIN and biometric sign-in, Secure Code, QR journeys, and device lifecycle.

Shared services

HID Authentication Service

Activation, credential validation, OTP, device registration, and authenticator policies.

Component Catalogue

Choose a channel to review the included components. Open a component to view its role, supported actions, and relevant configuration choices.

Onboarding and Login Flow Selector

Select an authenticator choice to view the corresponding onboarding and login flows that may be configured. These flows provide a decision view; the exact availability depends on the selected component properties and deployed HID authenticators.

First factor and MFA formation

Login formation: SECURE_CODEAPPROVE
Use Secure Code as the first factor and HID Approve as the configured MFA step.

Onboarding

Validate activation details and begin Secure Code device enrollment.
Register the device through QR or manual activation.
Complete HID Approve device registration as the configured MFA step.
Finish onboarding after the required device and factor setup succeeds.

Login

User generates or enters Secure Code as the first authentication factor.
The service validates Secure Code.
HID Approve is invoked as the configured MFA step.

Onboarding

Validate activation code and create a policy-compliant Static Password.
Register the Secure Code device through QR or manual activation.
Validate the new Secure Code and complete enrollment.

Login

User enters username and Static Password.
The service validates the first factor.
User generates and enters Secure Code for MFA validation.

Onboarding

Validate activation details and create a policy-compliant Static Password.
Register the HID Approve device through QR or manual activation.
Complete the Approve registration and finish enrollment.

Login

User enters username and Static Password.
The service validates the first factor.
User approves the HID Approve push request as the MFA step.

Onboarding

Validate activation details and create a Static Password.
Verify the registered mobile number.
Send and validate the SMS OTP to complete enrollment.

Login

User enters username and Static Password.
The service sends an OTP to the registered mobile number.
User enters the SMS OTP to complete MFA validation.

Onboarding

Validate activation details and create a Static Password.
Verify the registered email address.
Send and validate the Email OTP to complete enrollment.

Login

User enters username and Static Password.
The service sends an OTP to the registered email address.
User enters the Email OTP to complete MFA validation.

Onboarding

Onboarding formation: SECURE_CODE + APPROVE

Validate activation details and provision the Secure Code device.
Complete HID Approve device registration as the MFA step.
Complete the onboarding success journey.

Login

Login formation: USER_ID_LESS + NO_MFA

User completes the user-ID-less first-factor experience.
No additional MFA screen is configured for this login formation.

Onboarding

Validate user activation details.
Display the available FIDO authenticator or passkey registration option.
User follows the browser or platform instructions to register the authenticator.
Validate the registration result and complete onboarding.

Login

Login formation: FIDO + NO_MFA

User selects FIDO as the first factor.
The browser or platform prompts for the registered authenticator or passkey.
No additional MFA is configured after successful FIDO validation.

Web Onboarding Users

Provides a web onboarding workflow for account activation and authentication-factor registration. The selected properties control the first factor and MFA path.

Area	Supported choices
First factor	Static Password, Secure Code, FIDO, OOB SMS OTP, or OOB Email OTP.
Second factor	Static Password, Secure Code, OOB SMS OTP, OOB Email OTP, hardware-token OTP, HID Approve, or no MFA.
Key outcomes	Activation validation, credential creation, device enrollment, passkey registration, and device friendly-name update.

User Authentication

Provides the web user-login experience. The first factor and MFA screens are determined by component properties. Version 12.0.0.

Area	Supported choices
First factor	Static Password, Secure Code, FIDO, or User ID Less.
MFA	Secure Code, OOB SMS OTP, OOB Email OTP, HID Approve push, hardware-token OTP, or no MFA.
Key functions	`logoutOnClick`, `getRmsSessionid`, success and failure callbacks, loading and context-change events.

User Management

Manages registered devices, new-device and FIDO registration, password changes, and email or mobile-number updates. The web component can invoke a configured MFA step before sensitive changes.

Capability	What the component supports
Device lifecycle	Register, rename, suspend, reactivate, unassign, and remove devices.
Credentials and profile	Change password and retrieve or update email and mobile-number attributes.
Step-up choices	HID Approve, Secure Code, OOB SMS OTP, OOB Email OTP, hardware OTP, or no MFA, as configured.

Transaction Signing

Provides transaction authorization for web and mobile channels. The component is a non-UI transaction-details integration with an MFA experience determined by the selected signing factor.

Signing factor	Journey
HID Approve	Single-device or multi-device push approval, with device selection when needed.
Secure Code	QR or manual transaction-data entry in the mobile app generates an OCRA Secure Code for validation.
OTP SMS	Fetches registered communication details, sends OTP, validates the entered OTP, and returns the result to the transaction process.

Onboarding and Login

The principal mobile component for onboarding, sign-in, Secure Code generation, profile renewal, container deletion, and password-expiry handling. It supports activation-code and QR-code onboarding modes.

Area	Mobile behavior
Onboarding	Activation Code, QR Scan, and manual onboarding. Successful enrollment leads to PIN setup and optional biometric enablement.
Login	Single-user or multiple-user pre-login experience, protected by biometric authentication or PIN.
Supported operating systems	Android 8 and later; iOS 10 and later, as stated in the supplied material.

Mobile Transaction Signing

Supports Scan to Pay, Secure Code generation, push approval, and transaction-signing journeys initiated by the connected digital-banking application.

Use Scan to Pay to scan a QR code or enter transaction data manually.
Use PIN or enrolled biometrics before generating or signing with a Secure Code.
Return signed results to the HID Authentication Service for validation.

Approve Notification

Handles registered-device push notifications and the related mobile approval or decline journey. The mobile app receives the prompt, retrieves the transaction context, performs the selected local authentication, and sends the signed response for validation.

Mobile User Management

Supports profile and device actions for the active mobile user, including container renewal or deletion, PIN changes, biometric preference changes, and device-specific status information.

Detailed Component Reference

Each component below follows the same detailed structure used for the onboarding documentation: overview, key capabilities, and applicable flow guidance.

Web Components

Web Onboarding UsersDetailed reference

Component Overview

Attribute	Value
Component package	`com.hid.olb.onboarding`
Platform	Web
User interface	First-factor and MFA screens are added according to the selected component properties.
Functionality	User onboarding and authentication-factor registration.
Version	Version 12.0.0

Key Capabilities

Activation-code validation and guided user account setup.
Static-password creation with password-policy validation.
Secure Code device enrollment by QR code or manual activation, including friendly device naming.
OOB SMS or Email OTP enrollment.
FIDO2 authenticator or passkey registration through the web authentication platform.

Onboarding Workflow

User enters their username and activation code.
The component validates the activation details and displays the selected first-factor journey.
For Static Password, the user creates and confirms a policy-compliant password.
For Secure Code or HID Approve, the component displays QR or manual-registration information, validates device enrollment, and captures a friendly device name.
For OOB, the component sends and validates the OTP before progressing to the next configured factor.
For FIDO, the user registers a supported authenticator or passkey and is directed to the successful onboarding result.

Static Password: validate activation details, create and confirm a policy-compliant password, then continue to the configured MFA factor. Secure Code: validate activation details, register the device by QR code or manual activation, then update the device friendly name after successful registration.

Static Password Onboarding Flow

Step 1: Enter username and activation code, then select Verify

Step 2: Enter and confirm the new password

Step 2: Review password-policy validation

Step 3: Set the policy-compliant password

Secure Code/Approve Device Enrollment Flow

Step 2: Scan the QR code to register the mobile device, or activate manually

Step 3: Update the registered device friendly name

User AuthenticationDetailed reference

Component Overview

Attribute	Value
Component package	`com.hid.olb.loginComponent`
Platform	Web
User interface	First-factor and MFA screens are added according to the selected component properties.
Functionality	User login and authentication-factor validation.
Version	Version 12.0.0

Key Capabilities

Supports Static Password, Secure Code, FIDO, and User ID Less as the first factor.
Supports Secure Code, OOB SMS OTP, OOB Email OTP, HID Approve Push, hardware-token OTP, and no MFA as configured.
Provides success, failure, loading, context-change, and contact-support callbacks.

Login Flow

User enters the selected first factor.
The component validates the first factor with the HID Authentication Service.
If MFA is configured, the component displays the required factor screen.
After successful validation, the host application processes the success callback.

User ManagementDetailed reference

Component Overview

Attribute	Value
Component packages	`com.hid.olb.userManagement` and `com.hid.rms.olb.nonFinancialComponent`
Platform	Web
Functionality	Device management, new-device and FIDO registration, password changes, email updates, and mobile-number updates.
Version	Version 12.0.0

Key Capabilities

Register, rename, suspend, reactivate, unassign, and remove registered devices.
Change a password and retrieve the policy instructions for the new password.
Retrieve and update email and mobile-number attributes.
Invoke an approved MFA factor before sensitive changes.

Protected Action Flow

User selects a device or profile-management action.
The component shows the required action screen and requests the configured MFA factor.
The identity service validates the selected factor.
The component returns the action result to the host application and refreshes the displayed state.

Sensitive User Management actions require the configured MFA factor. The reference supports HID Approve, Secure Code, OOB SMS or Email OTP, or Static Password as configured.

Step 1: Open Registered Devices and select Register New Device

Step 2: Scan the QR code or use the manual invitation code to register the device

Step 3: The newly registered device appears in the device list

Edit Device Name Flow

Step 1: Select Edit Device Name from the device action menu

Step 2: Enter the new device name and select Update

Step 3: Validate the protected action with Secure Code or another configured MFA factor

Step 4: Device-name update success confirmation

Suspend Device Flow

Step 1: Select Suspend Device from the device action menu

Step 2: Validate the protected action with Secure Code or another configured MFA factor

Step 3: Device-suspension success confirmation

Step 4: The device status is updated to Suspended

Change Password Flow

Step 1: Enter the current password, new password, and confirmation

Step 2: Approve the protected password-change request

Step 3: Password-change success confirmation

Update Email Address / Mobile Number Flow

Step 1: Select Email or Mobile, enter and confirm the new value, then select Update

Step 2: Approve the protected email or mobile-number update

Transaction SigningDetailed reference

Component Overview

Attribute	Value
Component package	`com.hid.olb.TransactionSigningFlow`
Platforms	Omnichannel - Web and Mobile
Functionality	Transaction-details and MFA orchestration for transaction authorization.
Version	Version 12.0.0

Supported Signing Methods

HID Approve: single-device and multi-device push approval.
Secure Code: QR scan or manual transaction-data entry followed by OCRA Secure Code validation.
OTP SMS: OTP delivery to the registered number and validation before transaction completion.

Transaction Flow

User enters transaction details and selects the configured signing method.
The component displays the corresponding MFA experience.
The user approves, supplies Secure Code, or enters OTP.
The authentication result is returned to the transaction process for completion or rejection.

HID Approve Signing Flow

Enter payment details and select Approve

Single-device approval: push notification pending

Multi-device approval: select a registered device

Secure Code Signing Flow

Enter payment details and select Secure Code

Scan the QR code or enter payment Secure Code

Payment success after Secure Code validation

OTP SMS Signing Flow

Enter payment details and select Send OTP

Confirm the payment details before OTP delivery

Mobile Components

Onboarding and LoginDetailed reference

Component Overview

Attribute	Value
Component package	`com.hid.mb.MobileApproveSDK`
Platform	Mobile
User interface	Onboarding screens are added according to the selected onboarding mode: Activation Code or QR Scan.
Functionality	User onboarding, login, Secure Code generation, profile renewal, container deletion, and password-expiry handling.
Version	Version 12.0.0

Key Capabilities

Supports activation-code, QR-scan, and manual onboarding.
Creates a local service PIN and offers optional Face ID, Touch ID, or fingerprint authentication when supported by the device.
Supports single-user and multiple-user pre-login experiences.
Generates Secure Code for a connected web-channel login and supports Scan to Login journeys.
Handles profile renewal, device container deletion, PIN expiry, and key-expiry notices.

Onboarding Flow

User selects Enroll or Activate from the pre-login screen.
User chooses Activation Code or QR Scan. QR Scan can continue with camera permission, a web QR code, or manual username, invite-code, and service-URL entry.
The component validates the supplied activation or registration details.
User creates and confirms a PIN.
User can enable biometrics. The component shows the activation-success outcome after enrollment completes.

Login and Secure Code Flow

The active username is shown on the pre-login screen; multiple registered users can select the appropriate profile.
User verifies with biometrics or PIN.
For web Secure Code login, the user selects Secure Code, completes local authentication, and the component displays the generated code.
The generated code is entered in the web application for identity-service validation.

The reference supports Activation Code, QR Scan, and manual QR onboarding. After PIN setup, the user can opt into Face ID, Touch ID, or fingerprint authentication when the device supports it.

Activation Code Onboarding Flow

Step 1: Select Activation Code from Enroll/Activate

Step 2: Enter the username and activation code, then verify

Step 3: Create and confirm the service PIN

Step 4: Choose whether to enable biometric authentication

Step 5: Profile activation success

QR Scan Onboarding Flow

Step 1: Select QR Scan from Enroll/Activate

Step 2: Allow camera access to scan the web QR code

Step 3: Create and confirm the service PIN after registration

Step 5: Profile activation success

Mobile Login Flow

Single-user login: select the active username and verify

Single-user login: authenticate with the service PIN when biometrics are not enabled

Multiple-user login: select the registered username before verification

Mobile Transaction Signing and Approve NotificationDetailed reference

Component Overview

These mobile functions support Secure Code, Scan to Pay, and HID Approve push-notification journeys initiated by the digital-banking application.

Key Capabilities

Scan a transaction QR code or manually enter transaction data to generate a signing Secure Code.
Use biometric authentication or PIN before generating or signing an authorization response.
Receive HID Approve push notifications, review the request, approve or decline, and send the signed response for validation.

Flow

The web or mobile application initiates the signing or approval request.
The mobile component displays a PIN or biometric prompt when required.
The user completes approval, decline, Secure Code generation, or transaction signing.
The signed result is sent to the HID Authentication Service for validation.

Mobile User ManagementDetailed reference

Component Overview

Provides the mobile profile and device-management actions available to the active registered user.

Key Capabilities

Renew the profile container before expiry and delete a container when required.
Change the service PIN and update biometric authentication preferences.
Retrieve the active username and device-specific information for the current session.
Support the host application's navigation and UI changes during Secure Code and Scan to Login flows.

Operational Considerations

Recovery and lifecycle. Treat device removal, device suspension, and profile or PIN recovery as protected actions. The workflow material describes authenticating the user before sensitive changes and using service-desk recovery when authentication policies are blocked or a credential cannot be recovered.

Warn users before removing their only registered device because this can prevent future access.
Apply the configured thresholds for invalid Secure Codes, push challenges, and repeated OTP requests; show the configured recovery route when a threshold is reached.
For a lost device, locked HID Approve PIN, or additional-device registration, use the applicable activation or QR-based registration process.
Keep the web and mobile application implementations aligned on the selected authenticator, device type, and service configuration.

Content is based on the supplied HID Temenos Digital Component 12.0 documentation and HID Infinity component workflow material.