Nevis Authentication Cloud - Transaction Confirmation

Secure approval without unnecessary friction

A successful sign-in should not automatically authorise a sensitive action. Transaction confirmation adds a separate approval step for actions that require greater assurance.

Nevis supports secure digital identities without compromising user experience, compliance or sovereignty. With an Identity-First Security approach, organisations can build trusted digital relationships across customer, partner, citizen and machine identity journeys.

Transaction confirmation can help organisations to:

Present the details of a transaction for review before approval
Support biometric or PIN-based approval in the mobile Access app
Use transaction signing to associate an approval with a specific transaction
Reduce reliance on SMS one-time passwords, which can be exposed to SMS interception and SIM-swapping risks
Support confirmation flows for payments, terms acceptance and consent to data usage
Assess how transaction-confirmation workflows align with applicable security, privacy and regulatory requirements

Whether a confirmation meets a particular legal or regulatory requirement depends on the transaction, implementation and applicable rules. Nevis can support an assessment of the relevant requirements for your use case.

A controlled path to stronger transaction approval

Start with the transactions that carry the highest risk or require the clearest user confirmation. Define the approval journey, review integration requirements and introduce the workflow in a controlled rollout.

Discuss your transaction-confirmation requirements

How transaction confirmation works

A user initiates a sensitive action
A payment, account change, agreement or consent action requires confirmation.
The transaction details are presented for review
The user receives a transaction confirmation request in the mobile Access app and can check the details before making a decision.
The user approves or rejects the request
Approval can be completed with biometric verification or a PIN. The user can reject a request that is incorrect or unexpected.
The service receives the confirmation decision
Transaction signing supports a confirmation that is associated with the specific transaction being approved.

Transaction signing for specific approval actions

Transaction signing is designed to bind a user’s approval to the transaction details presented in the confirmation flow. This helps distinguish approval of a particular action from authentication at sign-in.

Nevis Authentication Cloud includes transaction signing alongside FIDO2/WebAuthn, push authentication, device binding, biometric authentication and risk-based multi-factor authentication.

This approach can support clearer confirmation journeys for actions such as:

Payment approvals
Changes to account access or details
Acceptance of terms and conditions
Consent to data usage
Document and agreement approval workflows

Review before approval

Presenting transaction details before approval helps users identify unexpected requests, incorrect information or changes they did not intend to authorise.

A separate confirmation step can help reduce the risk associated with compromised credentials, phishing, social engineering and transaction-data manipulation. It also supports a more deliberate approval process without requiring users to rely on passwords or SMS codes.

Biometric or PIN confirmation in the mobile Access app

Users can approve a transaction through biometric verification or a PIN in the mobile Access app. This keeps the confirmation action separate from the service where the transaction was initiated.

The result is a straightforward approval journey: review the request, confirm the details and approve or reject the action.

Built for flexible identity deployment

Nevis supports public cloud, private cloud and on-premises deployments. This gives organisations options when planning transaction-confirmation services alongside their identity, security and sovereignty requirements.

For implementation planning, assess the transaction types, user journeys, authentication methods and regulatory considerations that apply to your environment.

Transaction Confirmation

for High-Risk Digital Actions