
NoPass™
Passwordless workforce access and approval checkpoints for sensitive actions in your applications.
Explore NoPassSolutions / Financial services
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.

A customer arrives through a message or opens a page that looks like their bank. Before entering an account or approving an operation, they need more than visual familiarity with the brand.
In the FDA app-based relationship, the enrolled app verifies the authentication server connected to the service. The customer checks the comparison shown in the banking system and on their device before deciding.
The bank can authenticate the customer while giving that customer an active role in recognizing its request.
A banking application can hold a sensitive transaction and initiate a NoPass approval request. The customer receives the request on their phone and confirms on that device. The application uses the result before continuing.
This makes the customer’s decision part of the transaction workflow, beyond the earlier account sign-in.
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.
| Implementation question | Owner |
|---|---|
| Which payment state is held, and who may release it? | Banking application team |
| How is the responsible customer enrolled and recovered? | Identity and support teams |
| What happens after rejection, timeout or a changed payment? | Application and security teams |
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.