NoPass™ / Operation approval
A successful sign-in does not settle every later decision. Use NoPass to ask the responsible person to confirm a banking transaction, business operation or AI-agent action before it proceeds.
The system owner configures which operation requires approval and who should receive the request. This can be a bank customer confirming a transaction or an employee authorizing an action prepared by an application.
FDA brings the enrolled-device verification and visible comparison to that moment. The person can recognize the request and decide whether it should continue.
Transaction approval · interactive example
The application sends a NoPass approval request to the person responsible. Start the request in the application.
Open the push notification on the enrolled phone. The application waits while you check the request.
Supplier payment
Compare the black picture and number. If this is the request you intended, select Confirm on the phone, using the local confirmation configured for your device, such as fingerprint or Face ID.
Compare this picture and number with your phone.
501Do you approve this transaction?
501Approval received. The application still applies its own permissions and execution policy before carrying out the operation.
Your approval has been sent.
Try the highlighted button or use the controls below.
NoPass supplies the authentication or approval result. The connected application owns permissions, the held operation and its execution policy.
The application defines the action and responsible person.
The application holds the action while requesting a decision.
The person accepts or declines using the configured experience.
Approval is an input to the decision to proceed, not a replacement for business permissions.
Apply permissions and execution policy.
Keep the action from proceeding.
End or defer the request according to application policy.
| Actor or state | Responsibility |
|---|---|
| Application | Defines the operation, checks permissions and starts the approval request. |
| Responsible person | Reviews the intended request using the enrolled device. |
| Request identifier | Correlate the authentication result with the pending application operation. |
| Approved | Apply application authorization and execution policy. |
| Declined or expired | Keep the operation from proceeding in this example; offer the configured recovery or new-request path. |
| Changed operation | Define when a changed operation requires a new request before implementation. |
Explore the banking demo, or ask the team to walk through a transaction-confirmation scenario.
A business-banking payment request should be more than a familiar screen and an approval button. Explore how a connected banking application can request deliberate customer confirmation through NoPass and use that response in its transaction policy.
AI changes who can appear convincing and what software can do on our behalf. Identité® addresses two distinct moments: verifying the requesting service and asking a person to approve a sensitive action.
Define a useful decision before planning a wider rollout. Agree scope, responsibilities and success criteria with the team.
Identify the people, application and access or approval moment.
Map enrollment, account ownership, result handling and recovery.
Observe completion, recovery and support workload against agreed criteria.
Use the findings to decide what to change, expand or stop.
Passwordless workforce access and approval checkpoints for sensitive actions in your applications.
Explore NoPassConnect a customer account, an employee access point or a sensitive-operation checkpoint. Keep the application’s business logic and bring Identité authentication to the interaction that needs it.
