Biometric Approval
Use the biometric security already available on a customer’s phone, such as Face ID or Touch ID, to approve an action.

Initialising secure environment

Transaction Authentication
AuthKey is a transaction-authorisation layer that uses device-based biometric verification to approve payments and other high-risk actions without passwords or one-time codes.
The business challenge
A successful login does not prove that a customer intended a specific payment or high-risk action. Organisations need strong approval that remains clear and easy for the user.
Core capabilities
Use the biometric security already available on a customer’s phone, such as Face ID or Touch ID, to approve an action.
Cryptographically bind the approval to the specific transaction details, including the intended amount and recipient.
Remove passwords, codes and unnecessary app switching from the approval journey while retaining high assurance.
Apply stronger verification to sensitive payments, privileged actions and other decisions that require clear user intent.
Reference architecture
Bind the exact transaction to a registered device, verify the approver biometrically and return cryptographic proof of intent. The diagram below shows the product's distinct operating model, data paths and enforcement or decision points.
Example use cases
These examples explain the business purpose behind the architecture. Final scope, integrations and outcomes depend on your environment and implementation design.
A bank wants stronger assurance when a customer pays a recipient for the first time.
A large supplier payment requires executive sign-off and a traceable approval trail.
An administrator attempts a high-risk configuration or financial action.
Delivery path
The exact architecture depends on your environment, but the solution typically follows this practical operating flow.
The banking, payment or enterprise system sends the exact approval context to AuthKey.
The user sees what is being approved, including the relevant transaction or high-risk action information.
The user confirms with the phone’s supported biometric security instead of typing a password or OTP.
The system verifies that the authenticated approval is bound to the intended action before proceeding.
Typical use cases
Expected outcomes
DLAB's role
DLAB helps customers evaluate the fit, define use cases, coordinate solution demonstrations and proofs of concept, plan deployment with the principal and local partners, and establish the support path for production.
Arrange a solution workshop